iCR for Go User Guides
  • Table of contents
    • Introduction
    • Overview
    • 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
    • Using the Navigator
      • Connecting to the Navigator
      • Setting your User Password
      • 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
        • Limiting the files to be analyzed
      • 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. Authorizing Access to Your Source Code

Authenticating Bitbucket Access with a Cloud-Based VCS Repository

PreviousAuthenticating GitLab Access with a Private VCS RepositoryNextUsing the Navigator

Last updated 1 year ago

, describes how to create the OAuth credentials needed to access GitHub. This section adds the additional details if you are planning on using Bitbucket to access your source code.

Bitbucket also uses the OAuth standard to allow you to tell Bitbucket that your iCR for Go server is allowed to redirect login credentials for Bitbucket to authenticate. To set this up, login into Bitbucket and click on your login icon to drop down your user profile.

This opens another menu on the left.

That expanded menu is long, so scroll to the bottom to make sure that you see all the options.

The “OAuth consumers” page is where you tell Bitbucket to allow your Server to allow logins redirected from the Server.

Click on “Add Consumer” to add a new OAuth consumer for iCR for Go. This brings up the Add OAuth consumer page.

You also need to select both the Account: Read and the Pull requests: Write options. Then, select Save to complete the consumer authorization.

Click on the newly added consumer to display its items to be copied.

For the consumer “Name” use whatever you like. “iCR for Go” has been used in this example. You also must enter the redirect URL to the server. Bitbucket’s OAuth uses that to verify the authorization handshake. Enter the URL as your server’s IP address with port 3001 and the callback text. Using the example IP address from , enter: https://3.237.77.219:3001/api/login/bitbucket/return

As was noted in , once you have completed this step, you will need to copy the Key and the Secret. From here, the process is the same as outlined for .

Authenticating GitHub Access with a Cloud-Based VCS Repository Service
Authenticating GitHub Access with a Cloud-Based VCS Repository Service
GitHub Cloud
Authenticating GitHub Access with a Cloud-Based VCS Repository Service