This issue happened when I attempted to change the password of an existing LDAP Authentication User Directory configured in Stash.

      Typing a new password in the "Server Settings" -> "Password" field and then clicking the "Test Settings" button shows a "Connection test successful" message as expected.

      However, if the password is not re-typed in the password field a second time before clicking the "Save and Test" button, the correct password is not saved, and connections to the LDAP server fail. There is no indication that the password needs to be re-typed a second time after clicking "Test Settings".

      I noticed that the password field is populated with a placeholder mask after clicking "Save and Test", so maybe the mask is getting saved instead of the real password?

      I was able to reproduce this issue when accessing Stash 3.6.1 using Firefox 35.0.1 on Mac OS X Yosemite.

            [BSERV-7085] LDAP Credentials Not Persisted After "Test Settings"

            Kristy added a comment -

            This issue was fixed in Stash 3.10 when we updated to Embedded Crowd version 1.8.4 (the fix is contained in Embedded Crowd 1.8.2). In case the problem still exists in 3.10 or later, add a comment and we can re-open the issue.

            Kristy added a comment - This issue was fixed in Stash 3.10 when we updated to Embedded Crowd version 1.8.4 (the fix is contained in Embedded Crowd 1.8.2). In case the problem still exists in 3.10 or later, add a comment and we can re-open the issue.

            Reproduced in Stash 3.8.1 from various versions of Chrome and Internet Explorer (different Windows machines).

            Eitan Schichmanter added a comment - Reproduced in Stash 3.8.1 from various versions of Chrome and Internet Explorer (different Windows machines).

            Josh Dick added a comment -

            The two buttons I mentioned are on the screen for configuring an LDAP User Directory and are labeled "Test Settings" and "Save and Test", respectively.

            The password that needs to be re-typed is the field labeled "Password" under "Server Settings". It needed to be retyped after clicking "Test Settings" but before clicking "Save and Test"; otherwise, an incorrect password would be saved.

            Josh Dick added a comment - The two buttons I mentioned are on the screen for configuring an LDAP User Directory and are labeled "Test Settings" and "Save and Test", respectively. The password that needs to be re-typed is the field labeled "Password" under "Server Settings". It needed to be retyped after clicking "Test Settings" but before clicking "Save and Test"; otherwise, an incorrect password would be saved.

            sguio added a comment -

            Hi jodick
            Is the "Test Settings" Button you mention in the "Test Remote Directory Connection" Screen or under Server Settings --> Password

            Under Server Setting you have the options of "Quick Test" and "Save and Test"
            After the test it will offer you the option of "Test Settings" that is basically a tool to test that your LDAP users will be able to login in the LDAP (you can specify an user and a password, don't need to be admin) and the tool will try to login, this password will not be saved anywhere.

            We are not able to reproduce the problem with the password fields on the different screens, so please can you check where exactly is the password field you need to re-trype to get the password saved?
            Thanks

            sguio added a comment - Hi jodick Is the "Test Settings" Button you mention in the "Test Remote Directory Connection" Screen or under Server Settings --> Password Under Server Setting you have the options of "Quick Test" and "Save and Test" After the test it will offer you the option of "Test Settings" that is basically a tool to test that your LDAP users will be able to login in the LDAP (you can specify an user and a password, don't need to be admin) and the tool will try to login, this password will not be saved anywhere. We are not able to reproduce the problem with the password fields on the different screens, so please can you check where exactly is the password field you need to re-trype to get the password saved? Thanks

              khughes@atlassian.com Kristy
              5ed842ea992e Josh Dick
              Affected customers:
              4 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: