Siebel Security Guide > Security Adapter Authentication >

Comparison of Authentication Strategies


Table 10 highlights the capabilities of each authentication approach to help guide your decision. Several options are available for each basic strategy.

NOTE:  Comparisons do not apply for Siebel Mobile Web Client, for which only database authentication is available.

Table 10. Comparison of Authentication Approaches
Functionality
Database Security Adapter
LDAP or ADSI Security Adapter
Web SSO
Comments

Requires additional infrastructure components.

No

Yes

Yes

None

Centralizes storage of user credentials and roles.

No

Yes

Yes

None

Limits number of database accounts on the application database.

No

Yes

Yes

None

Supports dynamic user registration. Users are created in real-time through self-registration or administrative views.

No

Yes

Siebel Business Applications do not support the feature, but it might be supported by third-party components.

For Web SSO, user registration is the responsibility of the third-party authentication architecture. It is not logically handled by the Siebel architecture.

Supports account policies. You can set policies such as password expiration, password syntax, and account lockout.

Yes

Yes

Siebel Business Applications do not support the feature, but it might be supported by third-party components.

 

Among supported RDBMS vendors for the Siebel database, account policy (password expiration only) is supported only for IBM DB2 UDB.

For Web SSO, account policy enforcement is handled by the third-party infrastructure.

Supports Web Single Sign-On, the capability to log in once and access all the applications within a Web site or portal.

No

No

Yes

None

Siebel Security Guide Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices.