Authenticating GitHub Access with a Private VCS Repository
PreviousAuthenticating GitHub Access with a Cloud-Based VCS Repository ServiceNextAuthenticating GitLab Access with a Cloud-Based VCS Repository
Last updated
Last updated
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. For our example, we will assume that the URL to the private GitHub Enterprise server is:
http://vcs3.openrefactory.com
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:
You select “OAuth Apps” from the Developer Settings page. Then click on New OAuth App to configure iCR for Python. Note that there is one critical difference from the cloud-based version as shown in the view below. The callback URL is different and MUST replace the text: github with enterprise-github.
With that change, getting the Client ID and creating the Secret key is the same as described in the cloud-based VCS description).
With that change, getting the Client ID and creating the Secret key is the same as with the cloud-based VCS.
