You've already forked oauth2-proxy
mirror of
https://github.com/oauth2-proxy/oauth2-proxy.git
synced 2025-06-21 00:29:44 +02:00
2ecb2c64aa
* add new docs version 7.9.x * update to release version v7.9.0 * doc: add changelog summary --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Jan Larwig <jan@larwig.com>
26 lines
965 B
Markdown
26 lines
965 B
Markdown
---
|
|
id: bitbucket
|
|
title: BitBucket
|
|
---
|
|
|
|
1. [Add a new OAuth consumer](https://confluence.atlassian.com/bitbucket/oauth-on-bitbucket-cloud-238027431.html)
|
|
* In "Callback URL" use `https://<oauth2-proxy>/oauth2/callback`, substituting `<oauth2-proxy>` with the actual
|
|
hostname that oauth2-proxy is running on.
|
|
* In Permissions section select:
|
|
* Account -> Email
|
|
* Team membership -> Read
|
|
* Repositories -> Read
|
|
2. Note the Client ID and Client Secret.
|
|
|
|
To use the provider, pass the following options:
|
|
|
|
```
|
|
--provider=bitbucket
|
|
--client-id=<Client ID>
|
|
--client-secret=<Client Secret>
|
|
```
|
|
|
|
The default configuration allows everyone with Bitbucket account to authenticate. To restrict the access to the team
|
|
members use additional configuration option: `--bitbucket-team=<Team name>`. To restrict the access to only these users
|
|
who have access to one selected repository use `--bitbucket-repository=<Repository name>`.
|