PROVISIONING GATEWAY BAD VGOUSERDATA NAME WHEN A COMMA IN THE USER "CN" Firstname and Lastname (Doc ID 764044.1)

Last updated on FEBRUARY 21, 2011

Applies to:

Oracle Enterprise Single Sign-On Suite - Version: 10.1.4.0.3 to 10.1.4.0.5 - Release: 10gR3 to 10gR3
Information in this document applies to any platform.

Symptoms

Provisioning Gateway and ESSO LM with Store Credentials Under User Objects option activated. The AD user "cn" attribute usually has a  comma character to separate name and surname (i.e: Ex."CN=perez ortiz,  ignacio"). 
-->If used ESSO-LM Agent to add a new logon, a new "vGOUserData" object is created under the AD user object with the same "cn" attribute (with  a comma), 
-->But if a Provisioning Gateway is used, a new "vGOUserData" object is  created without a comma in the "cn". 

The logons added with Provisioning Gateway are not retreived by the LM Agent when it syncronize data Once both vGOUserData are created the Provisioning Gateway shows the following error when customer try to find users: 

Example:
Error: The storage has duplicated user object: perez ortiz, ignacio at 
LDAP://MADDC04.CEPSACORP.ES:389/CN=perez ortiz\, ignacio,CN=perez ortiz\, 
ignacio,CN=Users,DC=CEPSACORP,DC=ES

Cause

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