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:

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

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