Authenticating GitLab Cloud Access Using OAuth

To gain access to your GitLab cloud-based projects, you may choose to use OAuth to authorize iCR to access them. Here is how that is done.

Login into GitLab and hover over the sidebar to make it appear. Then, click on the User avatar icon at the top right of the sidebar.

The Preferences menu offers a number of configurable options. Again hover over the sidebar icon to have it reappear with new choices. OAuth is managed under the Applications option.

The “Applications” page is where you tell GitLab to use OAuth to allow logins redirected from the Server. Click on Add new application to open the form for configuring OAuth:

You can enter a helpful string, such as “User Guide iCR” for the Application name.

The Redirect URI will need to use the URL of your host system and must also specify the particular port number used to access the iCR Navigator. The default port number is 3001 although that could be changed by your system administrator so check with them if something other than the default port is being used. For these examples, we will use the default value of 3001`.

NOTE: If a URL has not been generated for your iCR server, you may substitute the IP address of the server.

In this example, we will use the sample URL:

https://qa2.openrefactory.com

The Redirect URI needs to specify the port and the callback string required to reach iCR. So, the full Redirect URI would be:

 https://qa2.openrefactory.com:3001/api/login/gitlab/return

You need to select both the Confidential and the api options. As was noted in Authenticating GitHub Access with a Cloud-Based VCS Repository Service, once you have completed this step, you will need to copy the Application ID and the Secret.

From here, the process is the same as outlined for GitHub Cloud.