Manage your credentials

Last updated: Nov 4, 2026

---

Your organization must give credentials to Fluid Attacks to access the repositories to test. As an alternative, your organization can allow access to repositories via Open Authorization (OAuth), and then credentials are not necessary.

The Source control tab is in the Integrations section of the Fluid Attacks platform. It shows the usual credentials, for example, user names with passwords, and the OAuth connections. From there, you can also start the OAuth connection to the supported providers: Azure, Bitbucket, GitHub, and GitLab.

View organization credentials table

The table in the Source control tab shows the credentials for use in the organization. All the groups of the organization can access them.

The table has this information:

• Name: The unique identifier of the credential
• Owner: The email of the person who registered the credentials on the platform, or of the last person who edited them
• Status: Shows if repositories that Fluid Attacks tests use the credentials, and which repositories use them
• Type: The authentication method, which can be one of these:
  • User and password: The classic combination of user name and password
  • SSH: A secure key to access remote systems. It is like a password, but more secure
  • Access token: A Personal Access Token for authentication with Azure DevOps
  • AWSROLE: Lets Fluid Attacks assume an Identity and Access Management (IAM) role in your AWS account
  • OAUTH: Delegated authorization that gives Fluid Attacks access to your repositories on supported providers (Azure, Bitbucket, GitHub, and GitLab)

Add credentials

You can connect the Fluid Attacks platform to an account on a supported code repository hosting provider. For the instructions, read "Import repositories fast and safely with OAuth".

If you do not use OAuth, do these steps to add new credentials for your organization:

1. Go to Integrations > Source control.

2. Click Add credentials.

3. Select Other method.

   

4. In the pop-up window, type a unique credential name (maximum 99 characters). Then, select the credential type. (If you select an AWS role, read the extra steps below.)

   

5. Give the applicable credentials. Then, click Add. The table shows the new credentials.

   

If you give Fluid Attacks access through cross-account IAM, the platform requests the Amazon Resource Name (ARN) of the role. Thus, do these extra steps:

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

   

2. Create an IAM role with the external ID. To learn how, read the instructions.

Edit credentials

To edit credentials, do these steps:

1. Go to Integrations > Source control.

2. Select the credentials. Then, click Manage credentials.

   

3. Click Edit.

   

4. In the pop-up window, make the changes. If necessary, activate the New secrets toggle to edit the secrets.

   

5. Click Edit to apply the changes.

Remove credentials

Read these points about the removal of credentials:

• When you remove credentials, the platform also removes them from all their Git repositories.
• When you remove a member from the organization, the platform also removes their credentials from the organization. You can remove the member only if the organization does not use these credentials (if it uses them, replace them in Scope first).

To remove credentials, do these steps:

1. Go to Integrations > Source control.

2. Select the credentials. Then, click Manage credentials.

3. Click Remove.

   

4. Confirm the removal in the warning window.

   

If the organization uses the credentials, you cannot remove them. In this case, the platform tells you to go to the Scope section and change the credentials of the repositories that use them. Then, go to Integrations > Source control again. Try to remove the credentials again.

Search the credentials table

You can filter the credentials table with the search bar. You can search the content of Name, Type, and Owner. Type the text that you want to find. The table then shows only the rows that match your search.