This page is maintained for older versions of Spira only. The latest documentation can be found at: https://spiradoc.inflectra.com

SpiraTest Administration Guide Help Viewer

1. Introduction
2. Installing SpiraTeam®
3. System Administration
4. Appendices
Search:
1. Introduction
2. Installing SpiraTeam®
3. System Administration
4. Appendices

3.8.3. LDAP Configuration

As described previously, you can configure SpiraTeam® to use an external LDAP server for importing new user profiles into the system, and for authenticating users – instead of having to store separate passwords inside SpiraTeam®. However you need to first configure the LDAP server settings. To do this, click on the “LDAP Configuration” link the Administration navigation:

You need to fill out the various configuration settings for your LDAP server, each of which is explained in more detail below:

  • LDAP HostThis should contain the name of the LDAP server that you want SpiraTeam to connect to together with the port number if it’s not the default of 389.
  • Use Secure Sockets Layer (SSL)You should select this check-box if your LDAP server requires use of the LDAPS secure protocol. Leave unchecked for unencrypted LDAP communication.
  • Base DN This should be the distinguished name of the object inside your LDAP server that contains the list of user accounts. This varies by the type of LDAP server, please consult your LDAP server documentation for more details.
  • Bind DN This should be the distinguished name of the user inside your LDAP server that will be used to authenticate against when importing users. If not provided, SpiraTeam® will try and authenticate with the LDAP server anonymously.
  • Bind Password The is the password of the user specified in the Bind DN field above.
  • Login AttributeWhen SpiraTeam® imports users from the LDAP server it needs to know the user attribute inside the LDAP server that it should use to generate the SpiraTeam® user-name. For most LDAP servers the appropriate attribute would be “uid”. However for Windows ActiveDirectory, the attribute “sAMAccountName” should be used instead.
  • First Name Attribute Providing this optional attribute will allow SpiraTeam® to automatically populate the first name field of the imported user instead of simply using the username as a placeholder.
  • Last Name Attribute Providing this optional attribute will allow SpiraTeam® to automatically populate the last name field of the imported user instead of simply using the username as a placeholder.
  • Middle Initial AttributeProviding this optional attribute will allow SpiraTeam® to automatically populate the middle initial field of the imported user instead of simply leaving it blank.
  • Email Address Attribute Providing this optional attribute will allow SpiraTeam® to automatically populate the email address field of the imported user instead of simply using the username@spiratest.com as a placeholder.
  • Sample User You can optionally enter a sample user and password to test that the user is correctly authenticated against the server. You can update the LDAP configuration without setting this, but if you do provide a sample user/password, it will not save the configuration unless the authentication succeeds. If you choose to enter it, the user’s name should be the fully-distinguished name of the user (e.g. CN=Sample User, CN=Users, OU=Headquarters, DC=, =Com).