Our LDAP does not contain a user's email address, but Stash seems to require it. We want users to be able to log in without creating account manually and then they define their email address, but what happens is the next time they log in their email address is empty again.
Is there any way around this issue while keeping the same workflow?
What happens is that every time a user logs into Stash, as you have LDAP configured, Stash will try to authenticate with LDAP and, once the credentials are correct, Stash will re-sync the user details with LDAP and the email configured for the user in Stash is replaced by what's configured in LDAP (empty).
Can you please look at Delegating Stash authentication to an LDAP directory - Copying users on login and try to disable that option?
If this answer was helpful, please allow me to ask you to mark my answer as accepted in order to have it in the top of the thread, also helping other customers.
Thanks in advance!
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot