You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello,
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.
https://confluence.atlassian.com/bamboo0607/system-wide-encryption-966045950.htm
For example, we have a Bamboo java spec file with an SshTask()
SshTask().authenticateWithPassword("BAMSCRT@0@0@xxxxxndbnxxxxxTaDsxxxx==")
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