Authenticating GitHub Enterprise Access Using PAT

If you are using a private VCS on a private deployment, you can use a very similar process as described for the cloud-based VCS systems to access your local repositories. In this example, we show how you can use a Personal Access Token (PAT) to access your GitHub Enterprise repositories.

Your first step is to login into the GitHub Enterprise server. Once logged in, go to your user icon and click on it to get this user pull-down menu:

The Developer Settings page will present you with various options for authorizing iCR. We want to use a PAT, so pull down the Personal access tokens menu and ckick on Tokens (classic). This will open the Personal access tokens (classic) page where you can click on Generate new token (Classic) to create your new Personal Access Token.

This opens a page where you set the scope for the token to enable iCR to access your repositories.

Enter a Note to help you remember what this token is being used for. Also, set an Expiration interval for the token. When the token expires, iCR will no longer be able to access your repositories. Then set the following scope values:

• repo

• read:org under admin:org

• write:public_key under admin:public_key

• read:user under user

• user:email under user

With these scopes selected, click on Generate token to create your token.

Copy the PAT now as it will not be displayed again. You will need to present it to the Navigator when you first select GitHub cloud as your preferred VCS, as described in Selecting Your Source Code.