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

Plan specific encryption for secret variables in Specs?

Is there a way to have plan specific encryption for secret variables in Specs?

Currently, I can have a password variable in my build plan and export it as a Java spec and in the spec file it shows the encrypted text for the password. The problem is I or anyone who has access to the specs repo can copy that encrypted string out of that java spec and paste it into another spec file for a different build plan and that plan is able to decrypt it / use it.  Which then allows me to echo that password into a text file as an artifact and then boom I have the password. 

The encrypted output is the same cross build plans meaning if I encrypt "password1" it will be the same encrypted output in 2 different plans allowing anyone to copy that into their spec and use it.  Is there a way to have plan specific encryption for secret variables?

2 answers

Simon says:

` Short answer: no.

  Long answer: Indeed, as you observed, Bamboo uses reversible encryption with no salt. The same plaintext will always transform in the same cyphertext. Bamboo is a single security domain, demarcated by the authentication mechanisms. Any body with valid credentials will be able to copy and use any cyphertext. This single security domain extends to the users that have access to Specs source code, which, if you store specs in a repository may extend to all repository (for example git).

Apparently this single security domain architecture is by design:

Bamboo's current encryption feature should be regarded as a method of achieving obfuscation rather than a method of achieving confidentiality. '

Simon out.

0 votes
Jeyanthan I
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 06, 2020

Hi @Paul O_Brien ,

It is critical to isolate your Specs repository from users that you do not want them to access. If they have access to Bamboo Specs repository, they can certainly reuse the encrypted variables as you rightly understood.

I recommend you to introduce appropriate elevated permission to access this repository. This recommendation is also applicable for any plan configuration you do in the UI.

Hope that helps.


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events