1. Security Guide
  2. Remote Configuration Option for Developer Web Client

Remote Configuration Option for Developer Web Client

This option applies only to the Siebel Developer Web Client. The remote configuration option can be implemented in the following authentication strategies:

  • Security adapter authentication: LDAP, custom (not database authentication)

  • Web SSO authentication

With this approach, you create a separate text file that defines any parameter values that configure a security adapter. You configure all security adapter parameters, such as those in a section like [LDAPSecAdpt], in the remote file, not in the application configuration file.

Storing configuration parameters in a centralized location can help you reduce administration overhead. All Developer Web Clients can read the authentication-related parameters stored in the same file at a centralized remote location.

The following examples show how a remote configuration file can be used to provide parameters for a security adapter that is implemented by Siebel eService in a Web SSO environment. The following example is from the configuration file uagent.cfg for Siebel Call Center:

[InfraSecMgr]
SecAdptMode = LDAP
SecAdptName = LDAPSecAdpt
UseRemoteConfig = \\it_3\vol_1\private\ldap_remote.cfg

In this case, the configuration file ldap_remote.cfg would contain an [LDAPSecAdpt] section. It could be defined similarly to the example earlier in this topic, and would contain no other content. The application configuration file would contain the [InfraSecMgr] section as defined in the preceding example. It would not contain an [LDAPSecAdpt] section and, even if it did, it would be ignored.

To implement remote security configuration for Siebel Developer Web Clients, follow these guidelines:

  • The [InfraSecMgr] section in the Siebel configuration file must include the UseRemoteConfig parameter, which provides the path to a remote configuration file. The path is specified in universal naming convention format, for example, \\server\vol\path\ldap_remote.cfg.

  • The remote security configuration file contains only a section for configuring the security adapter, such as the [LDAPSecAdpt] section.

  • Each Developer Web Client user must have read privileges on the remote configuration file and the disk directory where it resides.