SAML2 SSO Configuration error On Java Cloud Service AS Service Provider When Integrating With SAAS AS Identity Provider
(Doc ID 2424107.1)
Last updated on JULY 20, 2018
Applies to:Java Cloud Service - Version N/A and later
Information in this document applies to any platform.
In a Java Cloud Service deployment, SAML2 SSO is desired to be achieved. Identity Provider (IDP) is Fusion SaaS and JCS will be Service Provider (SP). IDP fails to import SP metadata because it contains IP address instead of Fully qualified DNS names (FQDN).
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