I cannot find the solution or searching the wrong way. I have a multiple environments in organization and I did not have issues configuring JIRA & Atlassian to use different Crowd servers, etc test jira using test crowd.. There is a config file crowd.properties, but for Stash there is no such file and it is using the production crowd server. I could do that with adding new user directory in Stash administration, but I am automating deployment and need to change configuration files.
Yes, but my question is how can make test-bitbucket.example.com to authorize against test-crowd.example.com and prod-bitbucket.example.com to authorize against prod-crowd.example.com
Currently every my instance is authorizing against prod-crowd.example.com
For Jira/Confl I edited crowd.properties file.
I don’t understand this part because for example Confluence, changing to test Crowd in crowd.properties you are able to login only with users created on test Crowd. So I am asking is there a way to change crowd server not using UI. As I wrote before, for Confluence and Jira I changed Crowd server not using UI.
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot