Using an LDAP Server for Client Authentication

To enable client authentication from LDAP, you configure the application server using the tools supplied in WebLogic. The server is configured to authenticate all incoming connection requests against a particular security back-end infrastructure—usually LDAP, but most application servers support many other security protocols. This topic describes how to perform this task for the LDAP security system, but your application server documentation should be consulted for all possible options and configurations.

Note: If you are updating a previous installation of the SIMULIA Execution Engine on an application server instance that already has client authentication enabled, proceed to Mapping Security Roles with an LDAP Server. All other settings described in the next two sections (Configuring the LDAP Connection and Testing the Connection to Your LDAP Server) should be unchanged and do not need to be repeated.

The instructions in the following section assume the use of an LDAP server for authentication (specifically, Microsoft Active Directory; other LDAP servers would be configured in a similar manner). WebLogic can also be configured to authenticate with the local computer. In this case, only users that have been added as a local user on the server system will be able to log onto the SIMULIA Execution Engine. This setup may be adequate for small test environments, but it is not suitable for production deployments. Some familiarity with LDAP is helpful to properly configure WebLogic to use LDAP.


In this section:

Configuring the LDAP Connection
Testing the Connection to Your LDAP Server
Mapping Security Roles with an LDAP Server
Finalizing the ActiveDirectoryAuthenticator Settings