Bookshelf Home | Contents | Index | Search | PDF

Security Guide for Siebel eBusiness Applications > User Authentication Overview >

Implementing Database Authentication

---

If you implement database authentication, it will typically be for a Siebel employee application, such as Siebel Call Center or Siebel Sales.

To allow database authentication to be implemented, you must make sure that the Security Adapter Name parameter at all applicable levels in the Name Server does not indicate that a security adapter is being used.

For information about setting Name Server parameter values and the purposes of the parameters, see Name Server Parameters.

An administrator must perform the following tasks to provide a new user with access to Siebel applications and the Siebel Database in a database authentication environment:

Create a database account for the user. Use your database management features to create a database account for each user.
Create a record for the user in the Siebel Database in which the user ID matches the user name for the database account.

The way you add a user to the database depends on the application to which you are granting the user access. In all cases you add users to the database through an employee application, such as Siebel Call Center.

For information about adding users to the database, see Internal Administration of Users.

The following options are available if you implement database authentication:

User Password Encryption. Maintains an unexposed, encrypted password to a database account, while an unencrypted version of the password is provided to the user for logging in. When enabled, a simple encryption algorithm is applied to the password before it is sent to the database.
Secure Login. Transmits user credentials entered to a login form over Secure Sockets Layer (SSL).

Bookshelf Home | Contents | Index | Search | PDF