We recently built a new Oracle SOA suite environment with version 184.108.40.206. A particular service which is exposed through Gateway was throwing 401 Unauthorized error. There were no instances for this service in em console. So, we initially thought that issue might be with Gateway and analysis was directed towards it. From Gateway logs we found that back end (SOA service) was throwing 401 error.
When we checked soa access logs (usually located under server logs directory) we observed 401 errors for this service. But there were no instances in em console. When we tail the logs and hit the service multiple times from postman, we observed below error in logs.
<Jan 26, 2023 8:32:05,927 PM PST> <Error> <oracle.wsm.resources.security> <WSM-00008> <Login Exception: [Security:090938]Authentication failure: The specified user failed to log in. javax.security.auth.login.FailedLoginException: [Security:090302]Authentication Failed: User specified user denied.> <Jan 26, 2023 8:32:05,928 PM PST> <Error> <oracle.wsm.resources.security> <WSM-00045> <HTTP authentication/authorization failure.>
This soa composite’s service has http token service policy attached to it. See below screen grab.
Basically, client was sending wrong authentication details and as authentication was failing at the beginning itself, instance was not getting dehydrated. After correcting credentials issue at client side, we were able to get response from the service.
- August 23, 2023How we reduced SOA OSB provisioning from 4 days to 4 hours
- May 23, 2023rabbitmqRabbitmq Connection Error: javax.net.ssl.SSLHandshakeException: Invalid ECDH ServerKeyExchange signature
- March 24, 2023rcuSOA Suite 220.127.116.11 installation: Got exception when auto configuring the schema component(s) with data obtained from shadow table
- March 9, 2023rabbitmqNot able to start Rabbitmq Cluster: Cannot declare a queue ‘~s’ on node ‘~s’: ~255p