Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Shared/Multi-tenant Bamboo environment and Bamboo Specs encryption


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.


Thank you



0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events