Skip to main content
All CollectionsIntegrations and Trust CenterBitbucket integration
Bitbucket Data Center - Create an incoming link to connect to Keypup
Bitbucket Data Center - Create an incoming link to connect to Keypup
Arnaud Lachaume avatar
Written by Arnaud Lachaume
Updated over 3 weeks ago

To connect Bitbucket Data Center to Keypup, a Bitbucket administrator must configure an incoming link (OAuth provider) through the Bitbucket applications panel.

An incoming link allows a Bitbucket administrator to perform an OAuth flow between Keypup and your Bitbucket server and activate the connection.

Follow the steps below to create this incoming link and connect your Bitbucket server to Keypup:

1. (Optional) If your Bitbucket server is protected behind a firewall, you can allow Keypup API calls by whitelisting the following IP addresses:

  • 35.227.8.113

  • 34.139.100.4

  • 104.196.223.124

  • 34.23.243.137

2. Log into your Bitbucket server and go to Settings (cog wheel at the top right)

3. Go to the Application links section (located in the Integrations category)

4. Click on the Create link button at the top right of the screen, select type External application and direction Incoming, then click Continue:

5. Use the following details to configure the incoming link

Name

Keypup

Redirect URL

Permissions

Repositories:Read

6. Click on Save. Bitbucket will show you the identification credentials for the incoming link. The Client ID and Client secret will be required to complete the connection process on Keypup.

7. Note that you can always access these credentials from the Applications panel by clicking on the ... menu next to the incoming link and selecting View credentials

8. Back onto the Bitbucket Data Center connection process on Keypup, just click on Yes, I’ve created the incoming link

9. Fill out the connection details for your Bitbucket instance using the incoming link credentials generated in step 6.

Bitbucket servers with self-signed certificates

Keypup assumes and recommends the use of publicly recognized SSL certificates (e.g. from DigiCert, Let's Encrypt, etc.) for your server. API calls to your Bitbucket server always validate the SSL certificate in use. Expired or invalid certificates will eventually lead to the disconnection of your projects.

If your team uses a self-signed certificate on your Bitbucket server then you must disable SSL verification when setting up the connection. We do not recommend it but we still offer the option for convenience.

10. If the connection details are correct and we can establish a connection, you will be redirected to the projects page on Keypup. From there you will be able to select the projects to import.

11. As a next step, we recommend enabling webhooks for your Bitbucket server to send real-time updates to Keypup. See our article How to enable webhooks to Keypup.

Did this answer your question?