iCR for Python User Guides
iCR for Python 3.0
iCR for Python 3.0
  • Table of contents
    • Introduction
    • Overview
    • Getting Started
      • Installing iCR for Python
      • Managing your service
        • Opening Ports
      • Authorizing Access to Your Source Code
        • Authenticating GitHub Access with a Cloud-Based VCS Repository Service
          • Authenticating GitHub Access with a Private VCS Repository
        • Authenticating GitLab Access with a Cloud-Based VCS Repository
          • Authenticating GitLab Access with a Private VCS Repository
        • Authenticating Bitbucket Access with a Cloud-Based VCS Repository
          • Authenticating Bitbucket Access with a Private VCS Repository
          • Setting Bitbucket Server Credentials in the Navigator
    • Using the Navigator
      • Connecting to the Navigator
      • Setting your private passphrase
      • 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
        • Setting the scope of your analysis
      • 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 Directory pane
      • Filter by Category pane
      • 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
      • Capturing results for printing or sharing
      • Ending a reviewer session
    • When you are complete
    • Appendix – List of supported fixers
    • Appendix – Example Summary Report
    • Appendix - Sample Bug Listing
Powered by GitBook
On this page
  1. Table of contents
  2. Getting Started
  3. Authorizing Access to Your Source Code
  4. Authenticating GitLab Access with a Cloud-Based VCS Repository

Authenticating GitLab Access with a Private VCS Repository

PreviousAuthenticating GitLab Access with a Cloud-Based VCS RepositoryNextAuthenticating Bitbucket Access with a Cloud-Based VCS Repository

Last updated 1 year ago

If you are using a private GitLab VCS on a private deployment, you can use a very similar process as for the cloud-based systems to access your local repositories. For our example, we will assume that the URL to the private GitLab Enterprise server is: http://vcs.openrefactory.com

The steps are almost exactly the same as for . Once logged into the GitLab Enterprise server, click on the user icon to get the User menu.

The Applications page is slightly different from the Cloud version.

There is an additional entry Expire access tokens. You may leave this selected if you want to limit the time that iCR can access your GitLab Enterprise repositories. And, the callback URL is different. You MUST replace the text: gitlab with enterprise-gitlab as shown in the screen display above.

As before, select both the Confidential and the api options. Once you click on Save Application you get the success window with the Application ID and Secret as before. All remaining steps are as described for the .

GitLab Cloud instructions
GitLab VCS
Cloud GitLab