You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/cloud/bitbucket-server-integration-setup.md
+43-12
Original file line number
Diff line number
Diff line change
@@ -1,36 +1,67 @@
1
1
# Bitbucket Data Center / Server Integration Setup
2
2
## Private Packagist Cloud
3
3
4
+
<divclass="row column">
5
+
<div class="callout success">
6
+
<p>
7
+
This guide explains how to set up an OAuth integration for Private Packagist Cloud with Bitbucket Data Center / Server.
8
+
If you use their public service on bitbucket.org, these instructions are not relevant to you.
9
+
</p>
10
+
<p>If you are using our Self-Hosted product, please <a href="/docs/self-hosted/bitbucket-server-integration-setup.md">use this guide</a>.</p>
11
+
</div>
12
+
</div>
13
+
4
14
<divclass="row column">
5
15
<div class="callout warning">
6
16
<p>Note: Application Links using OAuth 2 are available since Bitbucket Data Center / Server v7.21. If you are using an older Bitbucket Data Center / Server version then consult the <a href="/docs/cloud/bitbucket-server-oauth1-integration-setup.md">Bitbucket Data Center / Server OAuth 1 setup guide</a>.</p>
7
17
</div>
8
18
</div>
9
19
10
-
## Initial Setup
11
-
From the organization settings page, select the "Integrations" subtab.
12
-
Hit the "Add Integration" button on the integrations listing page to get to the form below.
13
-
To set up a Bitbucket Data Center / Server integration with Private Packagist, start by selecting "Bitbucket Data Center / Server"
14
-
as the platform, enter the URL of your on-premise Bitbucket Data Center / Server into the base URL field and select OAuth 2 as the OAuth version as seen in the example below.
20
+
To allow your users to authenticate to Private Packagist with their Bitbucket Data Center / Server account, you'll
21
+
first need to create an integration in Private Packagist. This document walks you through the required steps.
From the organization settings page, select the "Integrations" subtab. Hit the "Add Integration" button on the integrations listing page to get to the form below.
25
+
To set up a Bitbucket Data Center / Server integration with Private Packagist start by selecting "Bitbucket Data Center / Server" as the platform, enter
26
+
the URL of your on-premise Bitbucket server into the base URL field and select OAuth 2 as the OAuth version as seen in the example below.
17
27
18
-
Copy the content from the "Callback URL / Redirect URL" field and follow the link to set up an Application Link.
28
+
A link to create a new OAuth application on your Bitbucket Data Center / Server instance will automatically be displayed.
Click on the link to setup an Application Link on Bitbucket Data Center / Server and select "External application" as type and "Incoming" as direction.
33
+
Do not submit the integration form yet, but copy the content from the "Callback
34
+
URL / Redirect URL" and follow the setup link to your Bitbucket Data Center / Server instance. The fields
35
+
Client ID and Client Secret remain empty for now.
36
+
37
+
In Bitbucket Data Center / Server, click on the "Create link" button and select "External application" as type and "Incoming" as direction.
22
38
23
-
39
+
24
40
25
41
After you click the button to continue, enter a name and the content from the "Callback URL / Redirect URL" from the Private Packagist form.
26
42
Select Repositories "Read" as application permission and save the form.
27
43
28
-
44
+
45
+
46
+
Once the form is saved, Bitbucket Data Center / Server will show you the Client ID and secret.
29
47
30
48
## Finish the Setup
49
+
Copy and paste the "Client ID" and "Client Secret" values back into the Private
50
+
Packagist integration form and submit the form with the "Create Integration"
51
+
button.
31
52
32
-
Once the form is saved, Bitbucket Data Center / Server will show you the Client ID and secret.
33
-
Copy them over to Private Packagist and save the integration.
Copy file name to clipboardExpand all lines: docs/cloud/bitbucket-server-oauth1-integration-setup.md
+25-5
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,16 @@
1
1
# Bitbucket Data Center / Server Integration Setup (OAuth 1)
2
2
## Private Packagist Cloud
3
3
4
+
<divclass="row column">
5
+
<div class="callout success">
6
+
<p>
7
+
This guide explains how to set up an OAuth 1 integration for Private Packagist Cloud with Bitbucket Data Center / Server.
8
+
If you use their public service on bitbucket.org, these instructions are not relevant to you.
9
+
</p>
10
+
<p>If you are using our Self-Hosted product, please <a href="/docs/self-hosted/bitbucket-server-oauth1-integration-setup.md">use this guide</a>.</p>
11
+
</div>
12
+
</div>
13
+
4
14
<divclass="row column">
5
15
<div class="callout warning">
6
16
<p>
@@ -12,18 +22,20 @@
12
22
</div>
13
23
</div>
14
24
15
-
## Initial Setup
25
+
To allow your users to authenticate to Private Packagist with their Bitbucket Data Center / Server account, you'll
26
+
first need to create an integration in Private Packagist. This document walks you through the required steps.
16
27
28
+
## Open the Add Integration form
17
29
From the organization settings page, select the "Integrations" subtab.
18
30
Hit the "Add Integration" button on the integrations listing page to get to the form below.
19
31
To set up a Bitbucket Data Center / Server integration with Private Packagist, start by selecting "Bitbucket Data Center / Server"
20
32
as the platform, enter the URL of your on-premise Bitbucket Data Center / Server into the base URL field and select OAuth 1 as the OAuth version as seen in the example below.
Click on the link to setup an Application Link on Bitbucket Data Center / Server. You will need the "Client Id" and the "Public Key" shown in the form.
@@ -32,7 +44,7 @@ Click on the link to setup an Application Link on Bitbucket Data Center / Server
32
44
33
45
For Bitbucket Data Center versions 7.21 and newer, select "Atlassian product" and not "External application" to be able to set up an OAuth1 link.
34
46
35
-
After you hit the button to create a new Application Link a configuration window may appear. If it does, verify that the url matches your Private Packagist URL and hit "Continue", otherwise skip this step.
47
+
After you hit the button to create a new Application Link a configuration window may appear. If it does, verify that the url matches the "Application URL for Link" (_https://packagist.com_) and hit "Continue", otherwise skip this step.
36
48
37
49
38
50
@@ -48,7 +60,15 @@ Click on the pen icon to the right of the application you just created to edit t
48
60
49
61
This is where we will need the "Client ID" and the "Public Key" that were previously generated on the Private Packagist integration form.
50
62
Enter the "Client ID" into the "Consumer Key" field, make sure the entire content of the "Public Key" field gets copied and the "Consumer Callback" field stays empty.
51
-
Submit the form and go back to Private Packagist.
63
+
Submit the form and go back to the list of integrations in Private Packagist.
64
+
65
+
### Share the Bitbucket login link
66
+
The final step is sharing your organization-specific login link with your users. Look for the "Login link" button next to
67
+
your newly created Bitbucket Data Center / Server integration on the integrations page, and copy the URL.
68
+
69
+
70
+
71
+
This link presents the option to authenticate with your Bitbucket Data Center / Server account and can now be used to log in to Private Packagist.
Copy file name to clipboardExpand all lines: docs/self-hosted/bitbucket-integration-setup.md
+30-12
Original file line number
Diff line number
Diff line change
@@ -2,32 +2,50 @@
2
2
## Private Packagist Self-Hosted
3
3
4
4
<divclass="row column">
5
-
<div class="callout warning">
6
-
<p>Note: The instructions on this page create an integration with the public Bitbucket at bitbucket.org. If you are trying to setup an integration with your own Bitbucket Data Center / Server consult the <a href="/docs/self-hosted/bitbucket-server-integration-setup.md">Bitbucket Data Center / Server setup guide</a>.</p>
5
+
<div class="callout success">
6
+
<p>
7
+
This guide explains how to set up an OAuth integration for Private Packagist Self-Hosted with the public service on Bitbucket.org.
8
+
If you use Bitbucket Data Center / Server instead, consult <a href="/docs/self-hosted/bitbucket-server-integration-setup.md">this guide for Self-Hosted</a>.
9
+
</p>
10
+
<p>If you are using our Cloud product at packagist.com, this page is not relevant to you.</p>
7
11
</div>
8
12
</div>
9
13
10
-
## Initial Setup
11
-
Hit the “Add Integration“ button on the admin page to get to the form below.
14
+
To allow your users to authenticate to Private Packagist Self-Hosted with their Bitbucket account, you'll
15
+
first need to create an integration in Private Packagist. This document walks you through the required steps.
16
+
17
+
## Open the Add Integration form
18
+
Go to the Admin section and hit the “Add Integration“ button to open the form to create your integration. If you've just
19
+
installed Private Packagist Self-Hosted and it is still running in Setup Mode, you do not need to log in. If the application
20
+
is no longer in Setup mode, you will have to log in with an admin account first.
To setup a Bitbucket integration with Private Packagist start by selecting "Bitbucket" as the platform and enter <i>https://bitbucket.org</i> as the base URL, as seen in the example below.
25
+
A link to set up the OAuth application on Bitbucket will automatically be displayed.
Do not submit the integration form yet, but copy the content from the "Callback URL / Redirect URL" and go to <ahref="https://bitbucket.org/account">https://bitbucket.org/account</a>. Find the "OAuth" menu item under "Access Management" and click on "Add consumer".
Copy and paste the "Key" and "Secret" values back into the Private Packagist integration form and submit the form with the "Create Integration" button.
Copy file name to clipboardExpand all lines: docs/self-hosted/bitbucket-server-integration-setup.md
+39-12
Original file line number
Diff line number
Diff line change
@@ -1,26 +1,44 @@
1
1
# Bitbucket Data Center / Server Integration Setup
2
2
## Private Packagist Self-Hosted
3
3
4
-
This guide explains how to setup an OAuth integration for Private Packagist Self-Hosted with Bitbucket Data Center / Server integration.
5
-
If you are using our cloud product at packagist.com, [use this guide](../cloud/bitbucket-server-integration-setup.md).
4
+
<divclass="row column">
5
+
<div class="callout success">
6
+
<p>
7
+
This guide explains how to set up an OAuth integration for Private Packagist Self-Hosted with Bitbucket Data Center / Server.
8
+
If you use their public service on bitbucket.org, follow <a href="/docs/self-hosted/bitbucket-integration-setup.md">these instructions</a>.
9
+
</p>
10
+
<p>If you are using our Cloud product at packagist.com, <a href="/docs/cloud/bitbucket-server-integration-setup.md">use this guide</a>.</p>
11
+
</div>
12
+
</div>
6
13
7
14
<divclass="row column">
8
15
<div class="callout warning">
9
16
<p>Note: Application Links using OAuth 2 are available since Bitbucket Data Center / Server v7.21. If you are using an older Bitbucket Data Center / Server version then consult the <a href="/docs/self-hosted/bitbucket-server-oauth1-integration-setup.md">Bitbucket Data Center / Server OAuth 1 setup guide</a>.</p>
10
17
</div>
11
18
</div>
12
19
13
-
## Initial Setup
14
-
Hit the “Add integration“ button on the admin page to get to the form below.
20
+
To allow your users to authenticate to Private Packagist Self-Hosted with their Bitbucket Data Center / Server account, you'll
21
+
first need to create an integration in Private Packagist. This document walks you through the required steps.
22
+
23
+
## Open the Add Integration form
24
+
Go to the Admin section and hit the “Add Integration“ button to open the form to create your integration. If you've just
25
+
installed Private Packagist Self-Hosted and it is still running in Setup Mode, you do not need to log in. If the application
26
+
is no longer in Setup mode, you will have to log in with an admin account first.
To setup a Bitbucket Data Center / Server integration with Private Packagist, start by selecting "Bitbucket Data Center / Server"
16
-
as the platform, enter the URL of your on-premise Bitbucket Data Center / Server into the base URL field and select OAuth 2 as the OAuth version as seen in the example below.
31
+
as the platform, enter the URL of your on-premise Bitbucket Data Center / Server into the base URL field and select OAuth 2
32
+
as the OAuth version as seen in the example below. A link to set up the OAuth application on your Bitbucket instance will automatically be displayed.
Copy the content from the "Callback URL / Redirect URL" field and follow the link to set up an Application Link.
36
+
## Create Application link
37
+
Do not submit the integration form yet, but copy the content from the "Callback
38
+
URL / Redirect URL" and follow the setup link to your Bitbucket Data Center / Server instance. The fields
39
+
Client ID and Client Secret remain empty for now.
21
40
22
-
## Configure Application link
23
-
Click on the link to setup an Application Link on Bitbucket Data Center / Server and select "External application" as type and "Incoming" as direction.
41
+
In Bitbucket, click on the "Create link" button and select "External application" as type and "Incoming" as direction.
24
42
25
43
26
44
@@ -29,12 +47,21 @@ Select Repositories "Read" as application permission and save the form.
29
47
30
48
31
49
50
+
Once the form is saved, Bitbucket Data Center / Server will show you the Client ID and secret.
51
+
32
52
## Finish the Setup
53
+
Copy and paste the "Client ID" and "Client Secret" values back into the Private
54
+
Packagist integration form and submit the form with the "Create Integration"
55
+
button.
33
56
34
-
Once the form is saved, Bitbucket Data Center / Server will show you the Client ID and secret.
35
-
Copy them over to Private Packagist and save the integration.
0 commit comments