First off, my apologies if I don't explain this very well. We have a loosely coupled multi-tenant, single instance, Bamboo 6.7.2 environment and would like to use some other mechanism than the System-wide encryption provided where the AES key is stored in $BAMBOO-HOME/xml-data/configuration/cipher.
For example, we have a Bamboo java spec file with an SshTask()
That value is encrypted using the shared cipher under $BAMBOO-HOME, it is conceivable that another group could decrypt that encrypted value.
We would like a way to somehow use our own cipher/key or ideally, a key per project.
There is no other option and our hands are tied, we must work in this 'shared/multi-tenant' Bamboo environment.
Any thoughts, ideas, suggestions with this would be greatly appreciated.
G’day Bamboo customers, Bamboo DC 8.1 is now available with it the following features and programs: SAML 2.0, OpenID Connect, and Crowd SSO In order to help admins with a simplified user manage...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events