Security Guide for Siebel Business Applications > Security Adapter Authentication > Using the LDAP/ADSI Configuration Utility >

About Configuration for Developer Web Clients

When you configure Siebel Developer Web Clients (see Step 5), parameter values are written to a configuration file you specify, such as uagent.cfg for Siebel Call Center. SecAdptMode and SecAdptName are defined in the section [InfraSecMgr]. Additional LDAP or ADSI parameters are defined in the [LDAPSecAdpt] or [ADSISecAdpt] section, or in a section using a nondefault name.

CAUTION:  The LDAP/ADSI Configuration Utility overwrites, rather than appends, relevant pre-existing sections in the configuration file, such as [LDAPSecAdpt] or [ADSISecAdpt]. To prevent losing important configuration information, back up the file before you begin. The LDAP/ADSI Configuration Utility saves an exact copy of the modified configuration file, using the form filename.cfg_bak—for example, uagent.cfg_bak. Do not manually create backup files with this type of name, or they will be overwritten by the utility.

You can specify a nondefault name for your security adapter by adding a new section using that name. For example, if you specified LDAPSecAdpt1 as the security adapter name, this will be the value of the SecAdptName parameter, and a section named [LDAPSecAdpt1] will be created in the configuration file. In this case, an existing section named [LDAPSecAdpt] will not be modified.

After you have configured one file, you can copy the relevant parameter sections to other configuration files where you want to use the same settings.

For more information, see Security Adapters and Siebel Developer Web Client, which also contains a sample section from the configuration file.