Build build job username and password
Asked by tarvinder91:

I am looking for embedding credentials in Bamboo to be used in bamboo tasks without requiring password for the username provided. For the SSH task, there is an option to provide Username and password as authentication :

[https://confluence.atlassian.com/bamboo/using-the-ssh-task-in-bamboo-306348532.html#:\~:text=the%20remote%20hosts.-,Authentication%20type,-Choose%20whether%20Bamboo](https://confluence.atlassian.com/bamboo/using-the-ssh-task-in-bamboo-306348532.html#:~:text=the%20remote%20hosts.-,Authentication%20type,-Choose%20whether%20Bamboo)

However, it is possible to use this option even without providing the password. I could not find any information as to how is this configured. I have seen such setup running and I want to replicate it in the new environment. So I want to provide only username in the field and want bamboo to use the password from 'somewhere'. However, there is no documentation that provides how it is done. Also, it is definitely not the shared credential option as it a different option. Please provide more info


Answers:
author: Kian Stack Mumo Systems
body: [@tarvinder91](/t5/user/viewprofilepage/user-id/5292215),

You can use plan variables <https://confluence.atlassian.com/bamboo/bamboo-variables-289277087.html>.

Passwords can be hidden from any logs/outputs so they are kept secure once they are put into the plan variable.

comments: author: tarvinder91
body: This unfortunately is not possible and doesnt answer the question. I will try to reframe my question: when using SSH Task, and when u select 'Username and password' option for Authentication, bamboo asks for Username to be used and not Password. My query is regarding how is this password configured. The snapshot is from a working configuration. We dont want to use optional Change password setting.

![20230814_171603.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/275107i1D44D21383CE027E/image-dimensions/273x363?v=v2 "20230814_171603.jpg")


author: Kian Stack Mumo Systems
body: [@tarvinder91](/t5/user/viewprofilepage/user-id/5292215),   

I'm sorry, I'm still not understanding what the problem is. It looks like you do not need to click on the "Change password" setting.


author: tarvinder91
body: Ok. Well that is exactly my question. In the above settings, feom where will the bamboo use the password and without using the Change password option. Because there is no empty field to supply password but only Username


author: Eduardo Alvarenga
body: [@tarvinder91](/t5/user/viewprofilepage/user-id/5292215),

Answering your immediate "reframed" question: If a user is already defined for a task, its password dialogue will remain hidden unless you click on "Change password". That means the referred username already has a password that has been defined during the Task creation or at a later stage.

The SSH Task will accept Username \& Password and SSH Private \& Public key authentication with either manual input or via [Shared Credentials](https://confluence.atlassian.com/bamboo/shared-credentials-424313357.html).

I agree with [@Kian Stack Mumo Systems](/t5/user/viewprofilepage/user-id/853673) that your initial description requires some further context. What do you mean by "*you* *want bamboo to use the password from 'somewhere'"*?

If you required passwordless authentication use SSH Private \& Public keys authentication.

Best regards,

Eduardo Alvarenga  
Atlassian Support APAC

**--please don't forget to Accept the answer if the reply is helpful--**


author: tarvinder91
body: Thanks for reverting fast. Your answer helps me to put the right questions in braces as this is exactly what I am looking for here:

If a user is already defined for a task (*how is a user defined for the task? I dont see any option to define a user for a task* ), its password dialogue will remain hidden unless you click on "Change password". That means the referred username already has a password (*where is this password stored? Where does it come from ?-this is what I initially referred as 'somewhere'?)* that has been defined during the Task creation or at a later stage.

If you can pls answer this it will be really helpful


author: Eduardo Alvarenga
body: Hello [@tarvinder91](/t5/user/viewprofilepage/user-id/5292215)

1. A user is defined on an SSH task when it is added to the Job (created).
2. Your screenshot shows the "Admin" username.
3. Passwords are stored in the Bamboo Database under the *build_definition* table, *xml_definition_data* column.

Sincerely,

Eduardo Alvarenga  
Atlassian Support APAC

**--please don't forget to Accept the answer if the reply is helpful--**


author: tarvinder91
body: [@Eduardo Alvarenga](/t5/user/viewprofilepage/user-id/4365410) Thank you very much for clarification. Indeed I verified that, when a new SSH task is added, it asks for password in the field, once saved, the password field is not shown and gets hidden next time you open that task. Seeing just the task, it seemed there is no password field but only username. I would suggest to add this info in the SSH task page saying that password in only asked in when new task is added and then the field is hidden, to provide more clarity to readers.