We have Confluence (6.2.4), Jira (7.4.0), Bitbucket (5.2.0) and Bamboo (6.0.3). All are using Jira as base user directory for all users and groups.
In Confluence we can allow user to have admin rights but he can't edit group memberships.
Same in Bitbucket, a bitbucket-admin level user can't edit group memberships.
But in Bamboo user with bamboo-admin level permissions can edit group memberships inside Bamboo. He can insert himself to all groups found from Jira. And when all user directories have been syncronized, he has gained full access to everything everywhere.
Why is Bamboo not using read-only user directory, or is there a way to block this behaviour in Bamboo, or has there been update to address this somewhere between 6.0.3 to 6.2.3?
Nope i did not because my brains apparently read that as a "Save" button due to its location. Thanks, that worked.
Admins can of course always turn that off again, make group changes and do the user directory synch.
But that could be fixed using Restricted Administrator Role found from same options. Once we assigned only that role to our old admin-level users, they manage to configure bamboo in needed way and can't edit the user groups any more.
Thanks for answers and pointing us to obvious road!
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
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