Bookshelf Home | Contents | Index | PDF     

Siebel Security Guide > Security Adapter Authentication > Process of Implementing LDAP or ADSI Security Adapter Authentication >

Configuring LDAP or ADSI Authentication for Developer Web Clients

This topic describes the tasks you must perform if you want to implement LDAP or ADSI security adapter authentication for Developer Web Clients.

This task is a step in Process of Implementing LDAP or ADSI Security Adapter Authentication.

To configure LDAP or ADSI authentication for Developer Web Clients, perform the following tasks:

Configuring Security Adapter Parameters for Developer Web Clients

For Developer Web Clients, security adapter parameters are configured in the configuration file of the application for which you are implementing LDAP or ADSI security adapter authentication rather than in the Gateway Name Server.

Parameters in sections of the application configuration file that directly pertain to security adapters apply, in this context, only to the Siebel Developer Web Client. These parameters are counterparts to the Siebel Gateway Name Server parameters listed in Table 14, Table 15, and Table 16.

To configure a security adapter for the Developer Web Client, provide parameter values, as indicated by the guidelines in Table 17, in the configuration file for the Siebel application for which you are implementing LDAP or ADSI security adapter authentication.

You can use a text editor to make changes to an application configuration file, or you can do so using the Siebel Configuration Wizard. For more information about editing an application's configuration file and about the purposes for the parameters, see Siebel Application Configuration File Parameters. For a list of Siebel application configuration files, see Siebel System Administration Guide.

Table 17. Siebel Application Configuration File Parameters
Section
Parameter

[InfraUIFramework]

AllowAnonUsers

For the AllowAnonUsers parameter, enter TRUE for LDAP or ADSI.

NOTE:  Set this parameter to FALSE if your Siebel application does not use functionality that requires anonymous browsing, such as anonymous catalog browsing or user self-registration.

[InfraSecMgr]

SecAdptMode

For the SecAdptMode parameter:

  • For LDAP, specify LDAP.
  • For ADSI, specify ADSI.

SecAdptName

For the SecAdptName parameter:

  • For LDAP, specify LDAPSecAdpt or another name of your choice.
  • For ADSI, specify ADSISecAdpt or another name of your choice.

[LDAPSecAdpt]

For parameters, see Configuring Security Adapter Gateway Name Server Parameters or Configuration Parameters Related to Authentication.

[ADSISecAdpt]

For parameters, see Configuring Security Adapter Gateway Name Server Parameters or Configuration Parameters Related to Authentication.

Setting a System Preference for Developer Web Clients

If you are configuring LDAP or ADSI authentication for the Siebel Developer Web Client, then you must set the SecThickClientExtAuthent. system preference to True, as described in this topic.

Setting the SecThickClientExtAuthent. parameter to True allows security adapter authentication for users who log in through the Siebel Developer Web Client. System preferences are enterprise-wide settings, however, the SecThickClientExtAuthent. system preference has no effect on security adapter authentication for users who log in through the Siebel Web Client.

Use the following procedure to specify a value for the SecThickClientExtAuthent. parameter.

To set the SecThickClientExtAuthent parameter

  1. Log in as an administrator to a Siebel employee application.
  2. Navigate to the Administration - Application screen, then the System Preferences view.
  3. In the System Preferences list, select the SecThickClientExtAuthent system preference.
  4. In the System Preference Value column, enter TRUE.
  5. Restart the Siebel Server.
    
Siebel Security Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.