-
-
Setup Code Repositories Applications
-
Bitbucket
-
How to install and use JetBrains IntelliJ Gateway as a Citrix published application
-
Use Citrix Secure Access and Citrix Secure Developer Spaces with VS Code
-
Configure AI Gateway routing in Citrix Secure Developer Spaces
-
Configure external MongoDB with X.509 authentication in Citrix Secure Developer Spaces
-
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Bitbucket Cloud Integration as Code Repository Provider
Follow these steps to create an OAuth App in Bitbucket Cloud to connect it to the platform:
- Navigate to OAuth Consumers:
- Using a Bitbucket account, go to the main organization settings and then to “OAuth consumers”.
-
You can follow this
https://bitbucket.org/[YOUR_DOMAIN_NAME]/workspace/settings/apito reach this menu directly. - Add a New Consumer:
- Click on the “Add consumer” button and set the following fields:
- Name: The name you want to give to the application. It will be public.
-
Callback URL: The URL should have a structure similar to
https://example.com/oauth/apps/callback, where “example.com” should be replaced with the proper domain name. This URL can be seen from the admin panel of the Secure Developer Spaces platform. - This is a private consumer: This should already be selected by default; leave it as it is.
- Scopes: Select “Read” under the Account section and “Write” under the Repositories section, and “Read” under the Pull requests section. This can also be checked in the Secure Developer Spaces™ Platform when clicking the “Add Bitbucket” button.
- Complete the Registration:
- After clicking the “Save” button, you will be presented with the Client ID (called Key) and Secret, which you need to enter in the platform configuration.
Bitbucket Server or Data Center Integration as Code Repository Provider
In this section, we will see how to connect the Secure Developer Spaces platform to a self-hosted Bitbucket instance:
- Configure Secure Developer Spaces Platform:
- Go to the Secure Developer Spaces platform settings and open the “Code Repository Applications” menu.
- Click on the “Add Bitbucket” button.
-
Select the checkbox for “Bitbucket Server or Data Center (self-hosted)”.
- Set the Following Fields:
- Bitbucket App Name: It can be anything. This is what users will see when using this Code Repository Provider.
- Custom Domain: Enter the URL where the Bitbucket instance is hosted. If no scheme is given, HTTPS will be chosen by default.
-
Enforce Users to Connect: If selected, users will need to connect to Bitbucket before they can open their workspaces. This can prevent misconfiguration/permission issues on the user side.
- Complete the Registration:
- Click the “Create” button to complete the configuration on the Secure Developer Spaces platform side.
-
Save the “Bitbucket Server Public Key” for later use. This can also be found in the edit menu after clicking the “Create” button.
- Configure Bitbucket Instance (Version 7.20 or Later):
- Go to Administration > Applications > Application Links and click on “Create link”:
- Application Type: External application
- Direction: Incoming
- Click on continue
- Set a unique name
-
Redirect URL: Set to
https://example.com/oauth/apps/callback, where “example.com” should be replaced with the proper domain name. - Application Permissions: Account: Write, Repositories: Admin
- After clicking the “Save” button, enter “strong_network” for both Client ID and Client Secret.
- Configure Bitbucket Instance (Version 7.20 or Earlier):
- Go to Administration > Application Links.
- Enter the platform URL (e.g.,
https://example.com, where “example.com” should be replaced with the proper domain name). - Click on “Create new link”. If you see a “No response received” error, ignore it and click Continue.
- In the following menu, enter:
- Application Name: It can be anything.
- Application Type: Generic Application
- Service Provider Name: It can be anything (recommended: “strong_network”).
- Consumer Key: Set to “strong_network”.
- Shared Secret: Set to “strong_network”.
-
Request Token URL: Set to
http://example.com, where “example.com” should be replaced with the proper domain name. -
Access Token URL: Set to
http://example.com, where “example.com” should be replaced with the proper domain name. -
Authorize URL: Set to
http://example.com, where “example.com” should be replaced with the proper domain name. - Check “Create incoming link” and click Continue.

- In the following menu, enter:
- Consumer Key: Set to “strong_network”.
- Consumer Name: Set to “strong_network”.
-
Public Key: Enter the value that can be seen in the platform.
- Complete the Configuration:
- Click on Continue. The configuration is complete.
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.