We would like to make a Stash project and its repositories public, but read only and only accessible for users, that have a valid account in our Active Directory and thus are member of the Active Directory group "Authenticated Users". We want to ensure, that only internals have access to the code.
We already use Active Directory for authentication of our regular users.
Is this possible?
This is not something you can do with Stash, making a repository publicly readable makes it readable for everybody that has the url and that can connect to this url.
If your Stash instance is behind a firewall and not reachable from the internet I don't see a real problem with simply giving everybody on your company's intranet access to this repository.
If your Stash instance is reachabel from the internet I would look into making the repository not public.
Our instance is behind a firewall, but we simply have to many guests and externals in our network, that should not be able to browse the repositories.
Would it be possible to use the AD group "Authenticated Users" for a non public repository? I probably would have to create user accounts then or would the users be able to create the accounts themselves?
If your Stash instance uses AD for authentication and authorization you should be able to use that group to provide access to those users. I'm not sure if they can simply log into Stash (if you give that group basic stash user rights) or need to have an account created for them first. Cheers, Peter
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