Troubleshooting
Problem
The process for configuring Impact for LDAP is covered in the documentation and this is an example is meant to clarify how it is done.
Resolving The Problem
Because Liberty, unlike TIP, does not currently support federated repositories, when you configure Impact 7.1 for LDAP, you have to make sure that your Impact Admin User is pre-created in the LDAP repository beforehand, because the LDAP repository will be replacing the exiting one.
It is a good idea for this user to be the same for all repositories. The default username is impactadmin so in this example we will use this username.
After installing Impact 7.1 (specifying the user impactadmin with password impactpass), before you run confAuth4LDAP.sh, create this user in the LDAP repository you plan to use and you can then specify it as a parameter on the command line.
Also, before you run confAuth4LDAP.sh, you must edit your impactdap.properties file to set the values for the LDAP server you plan to use, including the LDAPBindDN (user you connect to the LDAP server with). You will need the password for this user when you run the command, so if this password is ldappass, you would use:
confAuth4LDAP.sh enable impactadmin impactpass ldappass impactpass
Where the first user and password are for the Impact Administration user in LDAP (that you will be using) and the last password is for the existing (file based) Impact administration user (as specified at install time).
Then, for example, if you want to disable the LDAP authentication (back to file based authentication), you would use:
confAuth4LDAP.sh disable impactadmin impactpass impactpass
Where the first impactadmin and impactpass are those in the file based repository and the last one is the existing LDAP Impact administrator password.
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21681232