Oracle Access Manager (OAM) Error Received In SAML Integrated Applications When A Delimiter ("|" Pipe) Is Used For A Header Response As Separator
(Doc ID 2989169.1)
Last updated on NOVEMBER 27, 2023
Applies to:
Oracle Access Manager - Version 12.2.1.4.221208 and laterInformation in this document applies to any platform.
Symptoms
Required to use "|" as delimiter for header responses
When used it shows the response headers from multi-valued attributes as expected, but the federation flow gets broken as any attributes sent in the assertion that are defined as user.attr.<name_of_the_attribute> are treated as multi-valued attributes and with "|" as delimiter there's a strange behavior as if the pipeline is after each character, so it sends the attribute as multi-valued, with each value being a character from the string that represents the attribute value.
Changes
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 |