Bookshelf Home | Contents | Index | Search | PDF |
Security Guide for Siebel eBusiness Applications > User Authentication Overview >
Database Authentication Overview
If you do not use an external authentication system, then you must create a unique database account for each user. When an administrator adds a new user to the database, the User ID field must match the username for a database account. The user enters the database username and password when the user logs into a Siebel application.
Figure 9 shows the authentication structure in an implementation using database authentication.
Database Authentication Process
The steps in a database authentication process are:
- The user enters a database account's username and password to a Siebel application login form.
- The Siebel Web Server Extension (SWSE) passes the user credentials to the authentication manager.
- The authentication manager interprets the credentials and passes them to the Application Object Manager.
- If the user credentials match a database account, the user is logged into the database and is identified with a particular user record whose user ID is the same as the database account's username.
Database authentication is the easiest to implement of the authentication approaches presented in this section.
Features Not Available for Database Authentication
Some of the features that other authentication strategies provide are not available with database authentication, including:
- Authentication that is independent of the database
- A single user-authentication method that is valid for Siebel applications and other applications on a Web site
- User self-registration
- External delegated administration of users
- Automated creation of users from the User Administration screen
Bookshelf Home | Contents | Index | Search | PDF |
Security Guide for Siebel eBusiness Applications Published: 23 June 2003 |