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
Last updated
If you are using a private GitLab VCS on a private deployment, you can use a very similar process as for the cloud-based GitLab VCS 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 Cloud GitLab. 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.
