Siebel Administration >  Changing user ID in Siebel

Sometimes users need to change their userid in Siebel. The most common reasons cited that I have
heard are marriages/divorces or correction of mistakes.
UserIDs can be changed by going to the Administration Data -> Employees screen. This field is
editable.

Changing usersIDs can lead to several errors in the Application and we do not recommend that this
is encouraged.

The Siebel Administrator can get this error message while changing userid

"An internal error has occurred within the authentication subsystem for the Siebel application. Please contact your system administrator for assistance.(SBL-DAT-00565)"

This error can happen if the authentication system uses LDAP authentication. Note that this is also an error in Siebel
Tools authentication. For description of that error, please check here - http://www.eir.me/siebel.php?art_id=86&cat=6

A second error message that can be seen is this

"The requested operation is not supported by your security adapter. Please contact your system administrator if you feel the operation should have been supported.(SBL-DAT-00567)"

This happens when the user authentication is Database based (DB Security Adapter)

Please check if the value on 'Propagate Change' parameter (alias PropagateChange for LDAPSecAdpt
and DBSecAdpt_PropagateChange for DBSecAdpt) is set to True. If yes, User ID cannot be changed because it
attempts to update User ID on either Directory Server (for LDAPSecAdpt) or Database Server (for DBSecAdpt).

In server manager , the command to check this would be

list param PropagateChange for server SERVERNAME COMPONENTNAME show PA_ALIAS,PA_VALUE
or
list param DBSecAdpt_PropagateChange for server SERVERNAME COMPONENTNAME show PA_ALIAS,PA_VALUE

Setting the value of this parameter to True allows the user to change their password but not their userid.

Solution: Set this parameter to false. This will allow change in userids but it will make it impossible for user's
to change their passwords. An alternative to this could be to create a new custom Object Manager (OM) and
a new custom DBSecAdpt profile with DBSecAdpt_PropagateChange (or LDAPSecAdpt profile with PropagateChange) set to
False in order to use this OM and profile to change the User ID. Since only Siebel Administrators need to chenge
userids, this process can be used.

Even if a userid is changed without errors, several other steps need to be finished. Activities by default remain assigned
to the old userid. Check the field OWNER_LOGIN from s_evt_act. If the old userid had activities associated with it, these
activities will be associated to the old userid and not to the new id. This is the vanilla functionality in Siebel 7.7, 7.8
8.0 and 8.1.

To get an idea what data is still associated with the old user in your application do this.
Open Siebel Tools, switch to the flat view. Select "Field" in the Object Explorer and search the fields
Predefault value and Post Default Value equal to "System: Creator"

All these fields would have to be updated.

As you can see, a lot of components use this. All of these components may not be used in your project-
but there is a lot to search for.