Credential Manager

Important Note: The actions described here are visible only to Org Administrators. General users cannot access Credential Manager.

Credential Manager: Overview

Credential Manager (CM) is your encrypted “digital locker” inside AutoRABIT. Store usernames, passwords, SSH keys, tokens, and certificates once, then reuse them across repositories and integrations without re-entering secrets each time.

Key benefits:

  • Centralized, encrypted storage managed by ARM.

  • Role-based sharing (global vs. private).

  • Eliminates hard-coding credentials in jobs or scripts.

Create a New Credential

  1. Hover over Admin and click Credentials.

    Admin menu with Credentials option highlighted

  2. Click Create Credential.

    Create Credential button

  3. In the pop-up, enter a Credential name and choose a Credential Type:

    • Username with Password

    • SSH

    • HashiCorp Vault

    • SSH Certificate

    • Application Token (Enterprise only)

Username with Password

Provide the service username and password. Choose a Credential Scope:

  • Global – share with the team.

  • Private – visible only to you.

Username with Password credential form

SSH

Upload or paste your private key (optionally protected by a passphrase). ARM stores the key and uses it for Git operations over SSH.

SSH credential form with key upload

  • Recommended – SSH keys are more secure than user/password.

  • Choose Global or Private scope.

  • Paste or upload the private key file; ARM never exposes it in plain text.

HashiCorp Vault

Add HashiCorp Vault credentials once; ARM can now generate a new Vault Token automatically via AWS authentication whenever the old token expires.

HashiCorp Vault credential form with AWS Auth option

For details, see the dedicated HashiCorp Vault guide.

Authentication Using SSH Certificates

SSH certificates pair a public key with a signature from a trusted Certificate Authority (CA). A Git server that trusts the CA accepts any certificate signed by it.

  • Upload the certificate-signed key while creating the credential.

  • Supported for GitHub Enterprise Cloud orgs.

SSH Certificate credential form

Limitation: Available only for GitHub Enterprise Cloud.

Application Token (Enterprise Only)

Connect ARM to Jira via Personal Access Token (PAT) to meet enterprise compliance.

  1. Select Application Token as Credential Type.

  2. Paste the PAT generated in Jira.

  3. Click Save.

Application Token credential form for Jira integration

Need PAT access? Email [email protected]. How to create a PAT in Jira: Atlassian docs.

PreviousPermissionsNextDelegating Approvals to Another User

Last updated

Was this helpful?