Skip to main content

 –

Using JNDI to specify an LDAP server when using an authentication service

Suggest edit Updated on June 30, 2021

You can set up an authentication service to override or extend the default Pega Platform™ authentication process. You can enter a Java Naming and Directory Interface (JNDI) entry, which represents a directory located on the LDAP server. Using JNDI enables you relocate servers without having to reconfigure the application.

The JNDI syntax is dependent upon the server environment.

Using a JNDI entry with WebSphere

Enter the name used for the JNDI lookup. This value matches the value entered as the Provider URL in the authentication server instance. For example, enter pega/ldapURL.

To define the JNDI entry, do the following:

  1. Use the WebSphere administrative console and navigate to EnvironmentNamingName Space Bindings.
  2. Specify the Binding identifier. For example, pega
  3. Specify the Name in name space. This value matches the value entered as the Directory in the authentication service instance. For example, pega/ldapURL
  4. Specify the String value, which is the actual URL of the directory. For example, ldap://serverx:384

Using a JNDI entry with Tomcat

Enter the full JNDI reference that corresponds to the environment entry specified in the deployment descriptor and the prefix java:com/env. For example, enter java:com/env/pega/ldapURL

Here is an example of an environment entry:

<env-entry> <description><![CDATA[Generic LDAP URL entry]]> </description> <env-entry-name>pega/ldapURL</env-entry-name> <env-entry-value>ldap://serverX:384</env-entry-value> <env-entry-type>java.lang.String</env-entry-type> </env-entry>
Did you find this content helpful? YesNo

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us