The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Use LDAP authentication without mail attribute

Adam Nerderman
May 1, 2015

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?

2 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Adam Nerderman
May 6, 2015

This would stop the problem over the email being reset after logging in again, but it doesn't help us to keep the flow where a user can login without their account having to be manually created ahead of time.

0 votes
Felipe Kraemer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 6, 2015

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!

Kind regards,
Felipe Kraemer

 

TAGS
AUG Leaders

Atlassian Community Events