Manage your credentials | Fluid Attacks

Manage your credentials

In the Credentials section on Fluid Attacks' platform, you can manage credentials for accessing your digital assets and perform the connection via OAuth to the different providers.

View organization credentials table

Role required: User, Vulnerability Manager or User Manager

You can store your credentials at the organization level and use them in all the groups that make up the organization. To see the credentials that exist, you have to go from the initial page to the tab called Credentials.

Main Page

Here you can see the list of all the credentials created in the organization you are exploring. In total, the table has three columns which are described below:
Credentials table
  • Name: The name of the credential.
  • Type: Which type of credential it is, can be HTTPS, SSH, Azure DevOps PAT or Cross-account AWS IAM role. You can also see in this column the connection of the providers via OAuth.
  • Owner: The person who created the credential.

Add credentials

Role required: User Manager

To add a credential, you have to click on the Add credential button.

Add individual

Clicking on it will allow you to add via OAuth or individually.

Add other

Below we show you how to add it individually; if you want to know how to do it via OAuth, you can enter here.

When you click on Add other, you will get a pop-up window where you can add new credentials.

Add Credentials

Here, you will have to enter a unique credential name and select the credential type ( HTTPS, SSH, Azure DevOps PAT or Cross-account AWS IAM role).

In case you want to use cross-account IAM, you will be asked for the ARN of the role you are going to create.

Add AWS credential

For this, we will provide you with an external ID. This ID is unique and we will use it as a private key that allows us to assume the role you will create in a more secure way; that's why you must use it as is in the creation of the role. Click here for more information on how to create the role.

Note: Keep in mind that if your organization has more than one AWS account, you can create the role on as many of them as you need and provide the correct ARN when prompted while adding the respective credentials.

Edit credentials

Role required: User Manager

To edit an existing credential, you have to select which one you want to edit. A pop-up window will appear, where you have to click on the toggle that says New secrets to enable editing of the credential and change its information.

Edit Credentials

According to the Credential type will enable the fields for editing.

Remove credentials

Role required: User Manager

To delete a credential, you have to select which one you want to delete; a warning window will appear asking for your confirmation.

Remove Credentials

The following are some points to keep in mind regarding credentials:

  • If the credential is removed, it is also removed from all the git roots used.
  • When a member is removed from the organization, then their credentials are removed from that organization.
  • The owner of the credentials is the last one that edited the credential's secrets.

Search the credentials table

Role required: User, Vulnerability Manager or User Manager

The search bar filters the information contained in the columns of the table.