Authenticating GitHub Cloud Access Using OAuth
Last updated
Last updated
To gain access to your GitHub cloud-based projects, you need to authorize iCR to access them using OAuth. Here is how that is done.
This will open the page allowing you to add iCR to the set of approved third parties from which you will accept login redirect requests.
Clicking New OAuth App will open the window shown below.
You can enter a helpful string, such as “User Guide iCR” for the Application name. The Homepage URL will need to use the URL of your host system.
NOTE: If a URL has not been generated for your iCR server, you may substitute the IP address of the server.
For the purposes of this guide, we will use an example URL:
iCR uses a specific port communicate with the browser. 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, so that needs to be added to the Homepage URL. Using our example URL, you would enter:
The application description is optional so you can leave it blank. Note that this information will not necessarily be seen by anyone logging into GitHub. Once the OAuth app is created, Users will log in to GitHub using their private credentials and will not see this information.
The Authorization callback URL needs to use iCR's callback URL. So enter:
Clicking on “Register Application” opens a window that asks you to create the secret keys that you will use on your server to authenticate it with GitHub.
You will need both the client ID Ov23liSqjObQGq00SedY and the client secret 4455b7a77f61cfa3a90a2503359ac41144e9d80d. Copy and paste these values in a convenient place as you will need to present them to the Navigator when you first select GitHub cloud as your preferred VCS, as described in Selecting Your Source Code.
