Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Security Guide > Security Adapter Authentication > Implementing Database AuthenticationThis topic describes how to implement database authentication. Database authentication is typically implemented for a Siebel employee application, such as Siebel Call Center or Siebel Sales. Database authentication is configured as the default authentication method and is the easiest of the authentication approaches supported by Siebel Business Applications to implement. About Implementing the Database Security AdapterAlthough configuration might not be required, you can implement the database security adapter using the Security Adapter Mode (SecAdptMode) and Security Adapter Name (SecAdptName) parameters. The Security Adapter Mode and Security Adapter Name parameters can be set for the Siebel Gateway Name Server, 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). You can configure the Security Adapter Mode and Security Adapter Name parameters using Siebel Server Manager. To do this, you specify parameter values for a named subsystem (enterprise profile). For the Developer Web Client, parameters can be configured by editing the application configuration file directly. For Gateway Name Server authentication, parameters can be configured by editing the gateway.cfg file. 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
About Password ExpirationIf you use database authentication, then it is recommended that you implement database password expiration policies on the database server if this functionality is supported by your RDBMS. For example, it is recommended that you configure database passwords to expire after a defined time period unless they are changed. On some RDBMSs this functionality is provided by default; on others this functionality, if provided, must be configured. For information on the password expiration policies supported by your RDBMS, see the appropriate RDBMS vendor documentation. NOTE: Support for password expiration policies and database user account password change through Siebel Business Applications is available only on supported IBM DB2 RDBMS operating systems. |
![]() |
![]() ![]() |
Siebel Security Guide | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |