We want to migrate some git repositories to Stash. We need to create about 100 users. Would it be possible to enable public sign up (we use external user directory Microsoft Active Directory through LDAP) and let them register themselves and then give them permissions for the new project? It would be even better, since we know the user names from Active Directory, if we could grant permissions for them in advance, so they can use Stash right away. Would this be possible?

I could not find documentation about public sign up. Any hint would be very appreciated. Thank you.

Andreas

4 answers

There is a self sign-up option on the /admin/authentication page, but this allows the users to create a new user, so it will not use their pre-existing AD accounts.

If you are using AD, the best way is to put the users into groups in AD and give appropriate permissions to AD groups in Stash. This way, you can then use the same groups to give access to other resources (build server, issue tracker, etc.) and the membership in project/department/team/etc. groups needs to be changed in only one place if somebody joins/leaves the company or moves to a different position.

 

You cannot use AD authentication for Stash but can enable Public signup and give the permissions to users group. Once the user arrives, ask them to signup. All the users will be added to the group and can start using Stash

You can use AD authentication and as far as I understand, they are already doing that.

You first need enable self signup from Administration. I just tested it and it works.Please enable and try

0 vote

Andreas,

This option is available under "Administration Cog Icon >> Authentication". See screen below:

Administration - Stash 2015-04-09 17-07-56.png


I've written some additional information on the doc below:

I hope that helps!

PS: Stash doesn't write into External Directories, so that will create the users in the "Stash Internal Directory". bear in mind that, as an admin, you will have to grant this user proper Global Permission so the user will be able to login.

I think that here, you should probably be looking at configuring your External Directory as a "Delegated" type and "Copying Users on Login" as well as adding them to a "Default Group" instead.

Kind regards,
Thiago

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

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&nbsp...

1,751 views 1 5
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you