User Authentication

There are two different user identifiers with distinct roles in the User object: Userid and Login Id.

Identifier	Characteristics
Userid	• Used internally for authorization. • Passed to the database connection as the CLIENT_IDENTIFIER on the database connection. • Used for record ownership in some objects and in auditing, whereby it cannot be changed after the creation of any records by the user. • The maximum length of Userid is 8 characters.
Login Id	• Used for authentication to the security repository configured on Oracle WebLogic domain. • It can match the Userid or differ to reflect site standards. Unlike the Userid, the Login Id can be changed at any time to reflect changes in the organization such as name changes or acquisition. • The maximum length of Login Id is 256 characters. Note: The Login Id must match, in the same case, as the entry in the configured security repository for Oracle WebLogic.

Identifier

Characteristics

Userid

• Used internally for authorization.

• Passed to the database connection as the CLIENT_IDENTIFIER on the database connection.

• Used for record ownership in some objects and in auditing, whereby it cannot be changed after the creation of any records by the user.

• The maximum length of Userid is 8 characters.

• Used for authentication to the security repository configured on Oracle WebLogic domain.

• It can match the Userid or differ to reflect site standards. Unlike the Userid, the Login Id can be changed at any time to reflect changes in the organization such as name changes or acquisition.

• The maximum length of Login Id is 256 characters.

Note: The Login Id must match, in the same case, as the entry in the configured security repository for Oracle WebLogic.

When maintaining a user, it is important that the Login Id is only changed using the maintenance function, LDAP Import or any Inbound Web Service based upon the User object and not directly using other means (such as direct SQL). This due to the fact that a security hash is generated at maintenance time and is checked at login time. At application login time, if the security hash does not match, the user is not authorized to access your application. To ensure security hashes are correct, use the Synchronize Data Encryption function to reset the user security hash.