Hi, we are currently trying to configure TestSpira LDAP server settings. Ive found this LDAP Configuration document which describes the process, but something seems to be still missing. The challenge is I merely operate as a messenger, I do not have the actual rights to try different settings. What we currently know is that the firewalls should have been correctly opened and we should have the the correct configurations: LDAP host: address and port number we have been given by the administrator SSL: Tried both on and off Port: Tried both 389 and 636 Base DN: uid=spirauser,ou=admin,dc=[company name omitted],dc=fi // To my understanding this is the user created for TestSpira Bind DN: Empty Bind password: Password for the spirauser Despite of these, we are not able to successfully connect to the server. Is there something anyone could suggest we could still try? My own (still untested) ideas are as follows: 1) There are multiple sources saying that defining the user with UID instead of CN results into different primary keys . Could this be an issue here, although the user was specifically created with UID. 2) By reading the previously mentioned documentation it doesnt state that the Bind DN is a mandatory field, but I got the impression that the created user should be in Bind DN field rather than in Base DN field. Documentation describes Base DN as the root node and Bind DN as the user to log in with . We specifically do not want to use the anonymous user, but a valid user with username and password. So we should specify the Base DN as something else and swap the user into the Bind DN field? Thanks, -Sami en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spiratest/issues-questions/1947.aspxthreadId=1947Sami Suikki (sami.suikki@arek.fi)ldap testspira Hi, we are currently trying to configure TestSpira LDAP server settings. Ive found this LDAP Configuration document which describes the process, but something seems to be still missing. The challenge is I merely operate as a messenger, I do not have the actual rights to try different settings. What we currently know is that the firewalls should have been correctly opened and we should have the the correct configurations: LDAP host: address and port number we have been given by the administrator SSL: Tried both on and off Port: Tried both 389 and 636 Base DN: uid=spirauser,ou=admin,dc=[company name omitted],dc=fi // To my understanding this is the user created for TestSpira Bind DN: Empty Bind password: Password for the spirauser Despite of these, we are not able to successfully connect to the server. Is there something anyone could suggest we could still try? My own (still untested) ideas are as follows: 1) There are multiple sources saying that defining the user with UID instead of CN results into different primary keys . Could this be an issue here, although the user was specifically created with UID. 2) By reading the previously mentioned documentation it doesnt state that the Bind DN is a mandatory field, but I got the impression that the created user should be in Bind DN field rather than in Base DN field. Documentation describes Base DN as the root node and Bind DN as the user to log in with . We specifically do not want to use the anonymous user, but a valid user with username and password. So we should specify the Base DN as something else and swap the user into the Bind DN field? Thanks, -Sami Tue, 04 Dec 2018 08:09:40 -05002018-12-04T16:14:05-05:00/Support/Forum/spiratest/issues-questions/1947.aspxmessageId=3465Jim R (donotreply5@kronodesk.net) Hi Sami I would recommend logging a help desk ticket for this. Troubleshooting LDAP is tricky and the forums are probably not the best place for this! Thanks Jim Tue, 04 Dec 2018 16:14:05 -05002018-12-04T16:14:05-05:00/Support/Forum/spiratest/issues-questions/1947.aspx#reply3465