SAML SSO Configuration Issue between JCS (PAAS) acting as SP and Oracle SAAS(HCM) acting as IDP (Doc ID 2554172.1)

Last updated on DECEMBER 19, 2022

Applies to:

Java Cloud Service - Version N/A to N/A [Release 1.0]
Information in this document applies to any platform.

JCS SSO SAML integration with HCM embedded IDP.

User configured SAML 2.0 with Oracle SAAS (HCM) as IDP and Oracle Java Cloud Service (PAAS) as SP as described below:

After configuration has been completed, receiving a 403 Forbidden error when accessing the resource.

After receiving the SAML assertion from the IDP, we see the following error messages in the server log (debug enabled).

Debugging:

Enabled the following debugs on managed server that was configured for SAML and set the log level to DEBUG for server log and out file.

weblogic -> security -> Atn
weblogic -> security -> saml2
weblogic -> servlet -> internal
weblogic -> servlet -> DebugHttp

	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

Symptoms

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.