Create Users' Credentials
Last updated
Last updated
Important Note: This article is for Org Administrators in particular. The actions discussed in the article are not available to general users.
Credential Manager (CM) is the "digital locker" where ARM stores log-in credentials like usernames and passwords. It securely stores your credentials, so you only need to enter them once for each remote repository you access. Storing login information in the ARM CM saves you time when you frequently access a file shared on another machine.
Log into ARM with username xyz@autorabit.com, for example, then do the following:
Hover your mouse over the Admin tile and select the option for Credentials.
Click Create Credential.
On the next pop-up screen, enter a Credential name.
Choose a Credential Type from the drop-down field.
Username with Password
SSH
HashiCorp Vault
SSH Certificate
Password-based authentication requires the user to enter their username and password to create a credential.
Credential Scope lets you specify exactly what type of access you need.
Global: Credential to be accessed by the team
Private: Credential for private usage
SSH is an encrypted protocol used to administer and communicate with servers. SSH is a secure way to access a site’s server remotely. The user must generate a public/private key pair on the client machine to identify them on the servers. You can choose to protect it with a password. Entering it with no password means anyone with access to the key files has the same level of access as the user, and no password is required when the client connects to the servers. Protecting the keys with a password means that whenever the user connects to a server using those keys, the password for decrypting it is required.
Important Note:
We recommend using SSH-type credentials rather than password-type credentials for increased security.
Credential Scope lets you specify exactly what type of access you need.
Global: Credential to be accessed by the team
Private: Credential for private usage
Upload the Private key, if available on your local machine, or paste it into the clipboard provided.
You can now choose the AWS Authentication method while adding HashiCorp credentials to ARM to generate the Vault Token automatically whenever the existing token expires. Now the user does not have to update the token manually from the application when it expires. Click here for a more detailed article on this topic.
About SSH Certificates
SSH certificates allow one SSH key to sign another SSH key, resulting in an SSH certificate. A server that trusts the Certificate Authority (CA) can verify the certificate’s signature and trust the certificate and its associated metadata.
Learn more information about SSH certificate authorities at https://docs.github.com/en/enterprise-cloud@latest/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities
How is an SSH certificate different than an SSH key?
SSH uses key-based authentication with public key cryptography, while an SSH certificate-based authentication and attaches a signed certificate to each key to verify their identities. By using a certificate signed by a trusted CA, users can do away with passwords, which are not secure, given that passwords can either be stolen or cracked via brute force, and leverage a partially automated, trust-based certificate authentication process to gain access to systems.
How to add SSH certificates?
To give organizations more control over how their members access their repositories in GitHub, ARM now supports credentials of the SSH Certificate type. The user must upload the key for the SSH certificate while creating a credential. Then the user can later authenticate the repositories and add them inside ARM using the credential.
SSH certificates only allow access to repositories that belong to their organization.
Limitation: Adding SSH certificates is currently limited to organizations using GitHub Enterprise Cloud.
