Migrating from Database to LDAP Authentication

After you install Siebel Business Applications, the security adapter options provided for user authentication are a database security adapter, an LDAP security adapter, and a custom security adapter. If you want to implement LDAP security adapter authentication for a Siebel application that was previously configured to use database authentication, then review the information in this topic.

Considerations in Migrating to LDAP Authentication

There are a number of issues that you have to consider in deciding the most appropriate authentication method for your Siebel implementation. For example, some features, such as user self-registration, are unavailable with database authentication while some components, such as batch and system management components, must use database authentication. For information on the benefits and limitations of different security adapter authentication options, review the following topics:

• "Comparison of Authentication Strategies"

• "About Siebel Security Adapters"

• "Features Not Available for Database Authentication"

• "About Authentication for LDAP Security Adapter"

Migrating from Database to LDAP Authentication

The steps to migrate a Siebel application from database authentication to LDAP authentication are outlined in "Process of Implementing LDAP Security Adapter Authentication". In addition, you must perform the following steps:

1. Migrate your users from the Siebel database to the external directory server; create an entry in the external directory for each user to be authenticated.

2. (Optional) Archive any Siebel user database accounts that are not required for LDAP authentication from the Siebel database. Do not archive the following database accounts:

   • The default Siebel administrator account, SYSADMIN.

   • The default database account, for example, LDAPUSER, that is used by Siebel LDAP security adapter to connect to the Siebel database.