Community Component 25.2
Community Component Help

# BaseDN

The distinguished name (DN) that the Community componentuses to access the group object when you authenticate with an LDAP security repository, and you use GroupDN to specify a group that the user must belong to.

By default, Community uses the security details of the user who is logging on to the LDAP server to retrieve details stored in the group that you specify with GroupDN. You must set `BaseDN` if the user does not have permission to retrieve the details in the group object.

If you have set KeyUserName, Community also uses the `BaseDN` user to bind to the LDAP server and search for a user. In this case, you must set `BaseDN` if the LDAP server does not allow anonymous binding.

If you set `BaseDN`, you must specify a BaseDNPassword.

NOTE: When you are using a Kerberized LDAP server, either:

- Set BaseDN to the name of a user who can get a Ticket-Granting-Ticket within Kerberos, and BaseDNPassword to the password for this user.
- Alternatively, if you prefer not to have the username and password in the configuration file, you can run Community in an environment where a `kinit` has been performed by a user that can access LDAP using the SASL GSSAPI mechanism. Community uses the Kerberos credentials obtained by `kinit`, so in this case BaseDN and BaseDNPassword are not required.

Type: | String
Default: |
Required: | No
Configuration Section: | `MySecurityRepository`
Example: | `BaseDN=Distinguished Name`
See Also: | BaseDNPassword GroupDN KeyUserName

Copyright 2025 Open Text
Version 25.2 | Last updated April 2025

Send documentation feedback

Close

Send documentation feedback

To send feedback using your default email client, open an email window.

Otherwise, send your feedback and the information below to MFI-swpdl.idoldocsfeedback@opentext.com.

We appreciate your feedback!

Product: Knowledge Discovery Community Component 25.2

Topic Title: BaseDN