Applications Protected by SSO 10g Fail To Authenticate When The Username Contains Non-Standard ASCII, Non-Printable Or Accented Characters

(Doc ID 1406383.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Application Server Single Sign-On - Version: 9.0.4 and later   [Release: 10gR1 and later ]
Information in this document applies to any platform.


Single Sign-On (SSO) 10g integration with Oracle HTTP Server (OHS) 11g character conversion problem.

When a user attempts to access an application via OHS that is protected by SSO, and the username contains non-standard (or non-printable or accented) ASCII characters, such as c├ęcile for example, authentication fails, as if the accented character is corrupted in the username.  The application is therefore not accessible by this user.

The application works without any problems for usernames that contain standard ASCII characters.  It also works if the resource is protected by mod_auth instead of mod_osso, for all users.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms