Connection & Authentication
Last updated
Was this helpful?
Last updated
Was this helpful?
To use two-factor authentication in GitHub, create a personal access token first.
Create a personal access token and use it in place of a password when performing Git operations over HTTPS with GIT on the command line or the API. For detailed information, refer to
Register your GitHub Repository in ARM using the same token.
Short-term solution: Disable support for CBC encryption ciphers. Follow the procedures below to disable weak ciphers:
Run the following command to list the ciphers: - sshd -T | grep ciphers | perl -pe 's/,/\n/g' | sort -u
Edit the file - /etc/ssh/sshd_config and add what strong ciphers you want to have or place in this file as shown in the example below- Ciphers aes128-ctr,aes192-ctr,aes256-ctr
Now, restart your sshd service using the command: service sshd restart
Long-term solution: Enable the TLS 1.3 protocol.
Make sure you are entering the JIRA API token in the Password field while registering your JIRA plugin for the first time in the ARM application.
Follow the steps below to generate a new API token for JIRA:
Go to the link: .
Click on Create API Token and provide the label name and click on Create.
Once the token is created, you will be able to see the Your new API token popup. Click on the Copy to Clipboard.
Use the copied token as a password for creating/updating the credential in AutoRABIT.
Once updated please use the same credential to authenticate the JIRA.
Follow the below steps to register the repository:
Log in to your repository and click on Clone. It will give you an https and an ssh link.
To register the repository, copy the https link and paste it into ARM.
Make sure the repo clone you see before https isn't included in the link you paste in ARM.
Input the URL that begins with https.
While SSH Key-based authentication uses public key cryptography, SSH Certificate-based authentication attaches a signed certificate to each key to verify identity. By using a certificate signed by a trusted Certificate Authority, users can do away with the 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.
This is because you used invalid SSH keys to register your repository. Please use the correct SSH keys and try again.
When you try to create a new branch you must validate the master branch's 'src' folder path, then select the parent branch as master, and the 'src' folder path will be automatically set to the newly created branch.