About Implementing the Database Security Adapter

You implement the database security adapter using the Enterprise Security Authentication Profile (Security Adapter Mode) parameter and the Security Adapter Name (named subsystem) parameter. You can set these parameters for the Siebel Gateway, the Siebel Enterprise Server, for a particular Siebel Server, for an individual Application Object Manager component, or for the Synchronization Manager component (for Siebel Remote).

Note: To configure an individual Siebel Server or component to use LDAP at a later time, then you must configure the Enterprise Security Authentication Profile (Security Adapter Mode) and the Security Adapter Name (named subsystem) parameters as shown in Step 1 of the following procedure.

You can configure the Security Adapter Mode and Security Adapter Name parameters using the Siebel Management Console.

Caution: If you want to configure a server component or a Siebel Server to use different database authentication settings than those already configured at a higher level (that is, configured for the Siebel Enterprise or Siebel Server), then you must create a new database security adapter. If you do not, then settings you make reconfigure the existing security adapter wherever it is used.

The following procedure describes how to implement database authentication.

To implement database authentication

1. Specify that you want to use the database security adapter by setting values for the following parameters:

   1. Set the Security Adapter Mode parameter to DB.

   2. Set the Security Adapter Name parameter to DBSecAdpt, or to a security adapter (enterprise profile or named subsystem) with a different name.

   For more information about parameters for the database security adapter, see Authentication Related Configuration Parameters.

2. If you want to implement user password hashing, then set the Hash User Password parameter to True.

   For detailed information on this task, see Configuring User Password Hashing.

   User password hashing maintains a hashed password in the database account while an unhashed version of the password is provided to the user for logging in. When user password hashing is enabled, a hashing algorithm is applied to the user’s password before it is compared to the hashed password stored in the database. It is recommended that you implement password hashing for user passwords.

   Note: For database authentication, password hashing parameters are specified for a data source referenced from the database security adapter, rather than specified directly for the security adapter.

3. Provide each user with access to Siebel Business Applications and the Siebel database as follows:

   1. Create a database account for the user using your database management functionality.

   2. Create a Siebel user record in the Siebel database; the user ID must match the user name for the database account.

      You add users to the Siebel database through an employee application such as Siebel Call Center. For detailed information about adding users, see About Adding a User to the Siebel Database.

4. If you are implementing database authentication with an MS SQL Server database, then perform the task described in Implementing Database Authentication with Microsoft SQL Server.