Manage your credentials

Last updated: Mar 25, 2026

---

Fluid Attacks requires your organization to provide credentials to access the repositories to be tested. Alternatively, your organization can allow access to repositories via Open Authorization (OAuth), eliminating the need to provide credentials.

Both actual credentials (e.g., username and password pairs) and connections made with OAuth are registered in the Credentials section on Fluid Attacks' platform. From there, you can also begin the connection via OAuth to the supported providers, which are GitHub, GitLab, Bitbucket, and Azure.

View organization credentials table

The table in the Credentials section shows the credentials stored for use across the organization, meaning that they are accessible to all groups within the organization.

The table provides the following information:

• Name: The unique identifier for the credential
• Owner: The email of either the person who registered the credentials on the platform or the last person who edited them
• Status: Whether credentials are associated with repositories under evaluation by Fluid Attacks and, if so, which repositories
• Type: The authentication method, which can be one of the following:
  • User and password: The classic combination of username and password
  • SSH: A secure key used for accessing remote systems, similar to a password but more secure
  • Access token: A Personal Access Token used for authentication with Azure DevOps
  • AWSROLE: Allows Fluid Attacks to assume an Identity and Access Management (IAM) role in your AWS account
  • OAUTH: Used for delegated authorization to grant Fluid Attacks access to your repositories on supported providers (GitHub, GitLab, Bitbucket, and Azure)

Add credentials

If you wish to connect Fluid Attacks' platform with an account on a supported code repository hosting provider, refer to the instructions at "Import repositories fast and safely with OAuth".

If not going for OAuth this time, follow these steps to add new credentials to use across your organization:

1. Go to the Credentials section.

2. Click on Add credentials.

3. Choose Add manually.

   

4. In the pop-up window, enter a unique credential name (shorter than 100 characters) and select the credential type. (Read below what extra steps to follow if you are choosing an AWS role.)

   

5. Provide the relevant credentials and click on Add. The new credentials are then added to the table.

   

In case you choose to grant Fluid Attacks access through cross-account IAM, you are asked for the Amazon Resource Name (ARN) of the role. Therefore, you need to follow these extra steps:

1. In the pop-up window, copy the external ID provided by Fluid Attacks.

   

2. Create an IAM role including the external ID. To learn how to do this, read the instructions.

Edit credentials

Do the following to edit existing credentials:

1. Go to the Credentials section.

2. Select the credentials and click on Manage credentials.

   

3. Click on Edit.

   

4. In the pop-up window, make the desired changes and, if needed, turn on the toggle that says New secrets to enable editing them.

   

5. Click Edit to apply the changes.

Remove credentials

Bear in mind the following considerations about removing credentials:

• Removing credentials also deletes them from all associated Git repositories.
• Removing a member from the organization removes their credentials from the organization, and member removal is only possible if these are unused (if they are in use, you would have to replace them in Scope first).

These are the steps to delete credentials:

1. Access the Credentials section.

2. Select the credentials and click on Manage credentials.

3. Click on Remove.

   

4. Confirm the removal in the warning window.

   

If the credentials are in use, their deletion is prevented. In this case, you are told to navigate to the Scope section to change those credentials in the repositories that are using them. After this, you may go back to Credentials and retry the deletion.

Search the credentials table

You can filter the credentials table by using the search bar. You can search by the contents of Name, Type, and Owner. Just type what you are looking for, and only the rows whose content matches your search are shown.