Missed Team ’24? Catch up on announcements here.

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

Bamboo shared credentials, missing SSH option

arw-nd
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 20, 2018

Following your article here, I should be able to save the private key, however I only have the option of AWS.

 

Does anyone have any idea of what I need to do to enable the SSH option?

 

We are using Bamboo Server (On premise) version  6.6.1 build 60605 - 04 Jul 18

 

Thanks

1 answer

1 vote
Daniel Santos
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 23, 2018

Hello Adrian,

  • Have you added the SSH key at Cog >> Overview >> Shared credentials?
  • Can you share where you are trying to use the SSH key, in what task?
arw324
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 27, 2018

Hi @Daniel Santos,

Thanks for your reply,

This is my issue, under Cog >> Overview >> Shared credentials, there is no `SSH` option:

Bamboo-SharedCreds.png

I'm trying to add the shared SSH key, so that I can use it in tasks.

 

Many thanks 

Daniel Santos
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 27, 2018

It looks like the plugin Shared Credentials is disabled in your instance.

I was able to reproduce the same scenario by disabling its two modules:

  • SSH (sshCredentials)
  • Username and password (usernamePasswordCredentials)

Moving forward

  1. Try to enable the modules again:
    1. Admin page >> Manage add-ons
    2. Select All add-ons in the drop down
    3. Search for Shared Credentials
    4. Click add-on and then X of 2 modules enabled
    5. Click enable on each module disabled if there are any
  2. If you cannot enable the modules using the method above or if they show up as enabled, please try to restart the instance and check if this issue was fixed. It is possible that this issue was caused by a startup issue when loading the system add-ons.

In case this didn't help we will probably need to open a support case to investigate this further.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events