Bookshelf Home | Contents | Index | PDF |
Siebel Security Guide > Security Adapter Authentication > Requirements for the LDAP or ADSI DirectoryIf you implement LDAP or ADSI security adapter authentication with Siebel Business Applications, you must provide a directory product that meets the requirements outlined in this topic. The directory product you provide can be one of the directory servers supported by the security adapters provided with Siebel Business Applications, or another directory of your choice. The following options are available:
About Setting Up the LDAP or ADSI DirectoryTo provide user access to a Siebel application implementing an LDAP or ADSI security adapter, the Siebel application must be able to retrieve credentials to access the database and the user's Siebel user ID. Therefore you must set up a directory from which a database account and a Siebel user ID can be retrieved for each user. Your LDAP or ADSI directory must store, at a minimum, the following data for each user. Each piece of data is contained in an attribute of the directory:
You can use other user attributes to store whatever data you want, such as first and last name. Authentication options that you choose might require that you commit additional attributes. If you create a new attribute object for your directory to store Siebel attributes (for example, Siebel User ID), you can use the Private Enterprise Number that Siebel Business Applications has registered with the Internet Assigned Numbers Authority (http://www.iana.org) to provide a unique X.500 Object ID. This number is 1.3.6.1.4.1.3856.*. An additional type of data, roles, is supported, but is not required. Roles are an alternate means of associating Siebel responsibilities with users. Responsibilities are typically associated with users in the Siebel database, but they can instead be stored in the directory. Leave role values empty to administer responsibilities from within Siebel Business Applications. For more information, see Configuring Roles Defined in the Directory. About Creating the Application User in the DirectoryDepending on your authentication and registration strategies and the options that you implement for your deployment, you must define a user, called the application user, in the directory. The application user is the only user who can read or write user information in the directory. Therefore, it is critical that the application user has appropriate search and write privileges to the directory. For information on creating the application user, see Configuring the Application User. For ADSI authentication, it is recommended that you use the Active Directory Delegation Control Wizard to define privileges for users in the directory. NOTE: If you are configuring an ADSI security adapter, ensure that the application user is either a domain user or has access to the directory server. If the application user cannot access the directory server, the authentication process fails. LDAP Security Adapter RequirementsIf you are using LDAP authentication, you must install the IBM LDAP Client software that is provided by Siebel Business Applications. Siebel Business Applications uses DLL files provided by the IBM LDAP Client to communicate with the supported LDAP directory server product you have chosen to use. If the IBM LDAP Client is not yet installed, then you must manually install it. For IBM LDAP Client installation instructions, see About Installing LDAP Client Software. ADSI Security Adapter RequirementsIf you are running the Siebel Server in supported Microsoft Windows environments, and you are using ADSI authentication, you must meet the requirements described in this topic. For more information about some of these requirements, see your Microsoft Active Directory documentation. NOTE: Siebel Business Applications do not support Microsoft Global Catalog functionality.
Verifying the Active Directory Client InstallationThe following procedure describes how to verify that the Active Directory client is successfully installed. To verify an Active Directory client installation
|
Siebel Security Guide | Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |