WLS 10.3 - SAML 2 authentication failed, resulting in SOAP fault due to HTTP 500
(Doc ID 1092004.1)
Last updated on NOVEMBER 01, 2021
Applies to:Oracle WebLogic Server - Version 10.3 and later
Information in this document applies to any platform.
A Webservice and client using SAML 2 authentication which was tested to work fine in Glassfish 2.1.1 after deploying on WLS 10.3 fails, when the client on Glassfish invokes the Webservice (on WLS), it fails with SOAP fault due to HTTP 500 error, as below:
No custom authentication is used, with everything using WLS defaults. The SAML 2 tokens are generated by Sun Metro.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document