spk-logo-white-text-short2
0%
1-888-310-4540 (main) / 1-888-707-6150 (support) info@spkaa.com
Select Page

Using Credentials In Code In CloudBees SDA

Using-Credentials-in-Code
Written by Joshua Kling
Published on February 1, 2022

Credentials Are Tough By Design

Credentials in Cloudbees SDA are admittedly a little tricky to get to. This is by design.  If it were any easier, it could be a potential security risk. There is really just one way to use credentials in code, and it’s a multi-step process. Here are the steps:

  1. Set the credential.
  2. Attach it to a step.
  3. Use it.

Careful manipulation is required here, as the software requires very exact definitions to get to this information. Any single missed parameter or missing ACL will return an error code.

How To Set The Credential

It is very simple to set a credential in CloudBees SDA.  First, start at the project level, or go to the credential screen, and add a new cred. You’ll be able to add a name, description, username, password, and set it to a local or external credential. Once it’s set, hit OK and head to the location where you intend to use it.

where to edit credentials

Attachment

Once a credential is set, it’s available in any pipeline or procedure that can access that project. However, you will need to grant explicit access permission for the pipeline or procedure that will use it.  You do this through the attaching feature. From within a pipeline, the code for this command looks like this:

ectool attachCredential "<project name>" "<credential name>" --pipelineName $[/myPipeline] 
--stageName $[/myStage] --taskName $[/myTask]

In this case, all of these flags are important. Please note that if you call it from a procedure context, you’ll need to use –stepName instead of –taskName, as these are different from pipeline tasks.

Using The Credential

Once the credential is attached to a task or step, using it is a simple matter. Use these two lines of code to pull the username or password into any script or bash command:

ectool getFullCredential "/projects/<project name>/credentials/<credential name>" --value password
ectool getFullCredential "/projects/<project name>/credentials/<credential name>" --value userName

They can be set to variables or used inline, depending on the context, such as an API call to a third party tool. Credentials are a powerful tool in CloudBees SDA — they can be used for more than just basic authentication. You can save any kind of secret in the password field, including tokens, making them a convenient way to hide secure information with confidence.

If you have any questions about credentials in SDA, or need help getting started, reach out to us and we’d be happy to help.

Latest White Papers

Replacing DOORS with Next Generation ALM

Replacing DOORS with Next Generation ALM

IBM DOORS has remained a consistent tool for managing software requirements. However, it has not kept up with the modern landscape. Explore options such as DOORS NG and other next-generation ALM tools in this eBook.What You Will Learn In this eBook, you will discover:...

Related Resources

How Microsoft 365 Copilot Delivers 353% ROI with AI-Powered Workflows

How Microsoft 365 Copilot Delivers 353% ROI with AI-Powered Workflows

For small and medium-sized businesses (SMBs), every minute counts. Microsoft 365 Copilot is reshaping how teams work, helping organizations reclaim valuable time, improve decision-making, and accelerate growth. Plus, it does this all while achieving a projected 353%...

Unlocking Developer Productivity with Atlassian Compass

Unlocking Developer Productivity with Atlassian Compass

When companies develop software, speed and scalability are everything.  Yet, as organizations grow, complexity creeps in. Microservices multiply, ownership becomes unclear, and development slows.  Atlassian Compass is changing that.  Designed to bring visibility,...

Top Test Management Tools Every Software Team Should Know

Top Test Management Tools Every Software Team Should Know

Modern software teams may be faster than ever, but they can only release with confidence if they have strong testing practices in place. As distributed teams, hybrid QA models, and rapid DevOps cycles increase, test management tools have become the backbone of...