We're experimenting with setting up Stash and want to use it with Crowd. So far so good, but I am concerned that I think I've found a bit of a showstopper that might mean we have to look at an alternative solution ...
The issue we've got is around the username. Because our authentication platform has to support external as well as internal users, I've adopted email addresses as the value for "cn" in LDAP and firstname.lastname as the value for "uid" in LDAP. These map onto "User Name Attribute" and "User Name RDN Attribute" in Crowd.
This works really well with JIRA and Confluence but I think is going to be a bit of a problem with Stash because the Stash URLs have the username in them, like this:
and what the users are used to is something more like:
This is a bit optimistic of a question but are there any solutions to this, e.g. an add-on or similar?
We did consider the use of aliases but felt that the additional admin overhead of having to set the alias when a new user starts or when someone's name changes could become problematic.
I think we've shelved the possible use of Stash, for now at least.
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