My Oracle Support Banner

OAM 10g: OSSO Integration Fails with Users Having Special Character In Login Attribute (Doc ID 1155305.1)

Last updated on SEPTEMBER 21, 2016

Applies to:

COREid Access - Version: to - Release: 10g to
Information in this document applies to any platform.


After integrating OAM with Oracle SSO (Oracle Access Manager Integration Guide Part Number B25347-01) a subset of users are unable to authenticate. The SSO logs say it cannot find the user and returns a HTTP-500 Internal Server Error.

This happens when the user has a special character like ":" ,  in the userid that will be passed to the XXX_REMOTE_USER header variable.

However this user can be found when searching in OIDDAS.


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

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