Last updated on MARCH 08, 2017
Applies to:COREid Access - Version: 10.1.4
This problem can occur on any platform.
Steps to reproduce:
1. Configure the OAM Policy Domain to set a headervar containing the value of ObMyGroups on authentication success
2. Access an OAM-protected page that displays the HTTP Headers: the ObMyGroups header variable is displayed correctly showing the names of all the groups the authenticated user is a member of.
3. Add the user to a group with non-ASCII characters in the group name
4. Access the OAM-protected page to display the HTTP Headers again: the ObMyGroups header variable is displayed with null value
The ObMyGroups headervar should display the UTF8-encoded value for the colon-delimited list of group names e.g.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms