The Remote Server Credential Manager stores authentication credentials used by Remote Servers, so the same credentials can be reused across multiple Remote Server configurations without duplicating secrets. You store credentials once, reference them from any number of Remote Servers, and rotate them in one place when they change.

OAuth-based authentication methods (Box, Dropbox, Google Drive, OneDrive, SharePoint) are not managed through the Remote Server Credential Manager.

The Credential Manager is useful when multiple Remote Servers authenticate with the same credentials. For example, AWS S3 connections point to a bucket within a specific region, but IAM credentials exist at the AWS account level and can be used across regions. You store those credentials once and reference them for multiple Remote Servers. When the credentials change, you update them in one place and all associated Remote Servers pick up the change automatically.

Who Can Manage Credentials

Only Site Administrators can create, edit, or delete Remote Server credentials. This keeps ownership clear and prevents unmanaged or duplicated credentials from accumulating.

Creating a Credential

Each Remote Server credential requires a Name and Remote Server type, plus the necessary authentication information for the chosen server type. An optional Description field lets you store information about the credential, like its purpose or who owns it.

The authentication information required depends on the Remote Server type. Any Remote Server type that uses stored credentials rather than OAuth-based authentication can be used with the Remote Server Credential Manager.

Copying from an Existing Credential

When creating a new Remote Server credential, you can select an existing credential as a source. You can't copy credentials from one Remote Server type to a different type.

Authentication details like passwords, private keys, and other secrets are inherited from the source credential and are never exposed during this process.

You can override any of the copied details by providing new values when creating the credential. For example, to use the same SSH private key with a different username, copy an existing SFTP credential and provide a new username.

Using a Credential When Configuring a Remote Server

When adding or editing a Remote Server, you can select an existing credential from the Remote Server Credential Manager to use in the authentication section. If the credential you need does not yet exist, create it first, then select it in the Remote Server configuration.

Rotating a Credential

When a credential is shared by multiple Remote Servers, updating the credential updates the authentication used by all associated Remote Servers. After rotating a credential, verify that each affected Remote Server reconnects successfully.

Deleting a Credential

Deleting a credential removes it from future use. If any Remote Servers are currently using the credential, update those Remote Servers to use a different credential before deleting it.