I am evaluating Stash for purchase and I am having some trouble configuring it to work with our active directory server in house. I filled out the credentials in the user directory segment and the dns name for the DC. I ran the test and it passed.
I attempted to login using my AD credentials and received the error:
"The remote authentication server is not available. Please try again later."
I checked the log file and found the same error message repeated. Closer inspection of the log with debugging turned on revealed:
Caused by: javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903A9, comment: AcceptSecurityContext error, data 52e, v1db1 ]
which appears to be invalid credentials. What can I do to trouble shoot this and what could I have misconfigured to cause this? Why does it pass the test and then say its unavailable for login?
Do I have to manually create a stub user in stash for domain accounts first?
Ok so on a whim I decided to try and pre-add a domain user account to see if that was even a needed thing. When I went to the users page I saw it prepopulated with all sorts of domain users but all the WRONG ones. Turns out the DN container I listed was completely wrong. The error was not super indicitive of that but it kinda makes sense when you think about the error code 49 related to this issue.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs