OAM Metadata for Federation Generated With And Without Port Number Randomly
(Doc ID 2346704.1)
Last updated on JANUARY 16, 2018
Applies to:
Oracle Access Manager - Version 11.1.2.0.0 to 11.1.2.3.171017 [Release 11g]Information in this document applies to any platform.
Symptoms
For example:
- in metadata file without portnumber appear something like:
<md:SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
Location="https://LBservername.domain.com/oamfed/idp/samlv20"
ResponseLocation="https://LBservername.domain.com/oamfed/idp/samlv20"/>
-in metadata file with port number (not expected) appear something like:
<md:SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
Location="https://LBservername.domain.com:10332/oamfed/idp/samlv20"
ResponseLocation="https://LBservername.domain.com:10332/oamfed/idp/samlv20"/>
Changes
Configuring federation.
Cause
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 |
| Changes |
| Cause |
| Solution |
| References |