Unified Language User Guides
iCR User Guide 5.0
iCR User Guide 5.0
  • Table of contents
    • Introduction
    • Overview
    • Authorizing Access to Your Source Code
      • Authenticating GitHub Cloud Access Using OAuth
      • Authenticating GitHub Cloud Access Using PAT
      • Authenticating GitHub Enterprise Access Using OAuth
      • Authenticating GitHub Enterprise Access Using PAT
      • Authenticating GitLab Cloud Access Using OAuth
      • Authenticating GitLab Cloud Access Using PAT
      • Authenticating GitLab Enterprise Access Using OAuth
      • Authenticating GitLab Enterprise Access Using PAT
      • Authenticating Bitbucket Cloud Access using OAuth
    • Using the Navigator
      • Connecting to the Navigator
      • Setting your User Password
      • Updating your User Information
      • The Navigator top banner
      • The Analysis Engine status
      • Selecting Your Source Code
        • Using a cloud-based VCS
        • Selecting your branch
        • Using a private VCS
        • Using a local project
        • Limiting the files to be analyzed
      • Integrating with your bug tracking system
        • Integrating with Jira - Define Your Project
        • Integrating with Jira - Authorizing Access for iCR
        • Integrating with Jira - Connecting with iCR
    • Using the Analysis Engine
      • Initiating an analysis
      • Monitoring the analysis
      • Interrupting the analysis
    • Reviewing your results
      • Reviewer summary and filters
        • Filter by Severity
        • Filter by Category
        • Filter by CWE
        • Filter by OWASP
        • Filter by Directory
      • Reviewing a fix
      • Accepting a fix
        • Accepting a fix when integrated with your bug system
      • Rejecting a fix
        • Rejecting a fix when integrated with your bug system
      • Undoing a fix
        • Undoing a fix when integrated with your bug system
      • Rejected fix history
      • Providing feedback
      • Applying the fixes
      • Cases needing manual attention
      • Comparing Analyses
      • Capturing results for printing or sharing
      • Ending a reviewer session
    • When you are complete
    • Integrating iCR Into Your CI/CD Workflows
      • Jenkins Workflow
        • Installing the plugin
        • Configuring the plugin
          • Creating a Personal Access Token
          • Copying Your Repository's URL
        • Viewing the Results
      • GitHub Actions Workflow
        • GitHub Actions Overview
        • Preparing the GitHub Workflow
          • Environment Variables
          • User Supplied Secrets
          • Setting the User Defined Secrets Values
        • Executing the Workflow
      • GitLab CI/CD Workflow
        • GitLab CI/CD OverView
        • Configuring the GitLab Script variables
          • Environment Variables
          • User Supplied Variables
          • Creating a Personal Access Token
          • Setting the User Defined Variable Values
        • Executing the Workflow
      • Multiple Workflows
    • Appendix – Language Specific Fixer Lists
    • Appendix - Sample Bug Listing
    • Appendix - Getting a BitBucket App Password for JENKINS
Powered by GitBook
On this page
  1. Table of contents
  2. Authorizing Access to Your Source Code

Authenticating GitHub Enterprise Access Using PAT

PreviousAuthenticating GitHub Enterprise Access Using OAuthNextAuthenticating GitLab Cloud Access Using OAuth

Last updated 5 months ago

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