|
Security Guide for Siebel eBusiness Applications > Security Adapter Authentication >
Comparison of Authentication Strategies
Table 6 highlights the capabilities of each authentication approach to help guide your decision. Several options are available for each basic strategy. X indicates that Siebel Systems supports the feature (with applicable third-party components). (X) indicates that Siebel Systems does not directly support the feature, but it may be supported by third-party components. NOTE: Comparisons do not apply for Siebel Mobile Web Client, for which only database authentication is available.
Table 6. Comparison of Authentication Approaches
Desired Deployment or Functionality |
Database Security Adapter |
LDAP/ADSI Security Adapter |
|
|
Does not require additional infrastructure components. |
X |
|
|
|
Centralizes storage of user credentials and roles. |
|
X |
X |
|
Limits number of database accounts on the application database. |
|
X |
X |
|
Supports dynamic user registration. Users are created in real-time through self-registration or administrative views. |
|
X |
(X) |
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. |
X |
X |
(X) |
Among supported RDBMS vendors for the Siebel Database, account policy (password expiration only) is supported only for supported IBM DB2 Universal Database platforms. 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. |
|
|
X |
|
|
