Creating tokens for collaboration
If you are a collaborator in a project that supports Git integration, you must create your own personal access token to the Git repository associated with the project to use this integration feature to share assets across the project. Access tokens to Git repositories are managed at the user level, not at the project level.
To create a personal access token to enable accessing the project Git repository:
-
Click your avatar in the IBM Cloud Pak for Data banner and then click Profile and settings.
-
Click the Git integrations tab and filter by the platform used for Git integration in the project. Ask your project Git administrator which platform to select.
-
Create a new token.
-
Log in to the platform used by the project and follow the instructions to generate a new token with repository scope. The token must have read and write access to the repository.
If you are using Bitbucket Enterprise, your token must have Repository admin rights.
-
Copy the newly generated access token and paste it in the Git integration dialog window.
-
Optional for GitHub Enterprise, GitLab Self-Managed, and Bitbucket Enterprise: Ask your project Git administrator if you need to provide a self-signed certificate or override an existing certificate. If you do, paste the certificate details in PEM format in the Git integration dialog window.
-
For GitHub Enterprise, GitLab Self-Managed, and Bitbucket Enterprise only: Enter the domain name and your user name.
The domain name URL must use the
https
protocol used at the time the access token is created and is not allowed to end with a forward slash (/
). An example is:https://dse-bitbucket.mylab.mycompany:8443
. Note that existing Git Enterprise tokens that don't use thehttps
protocol, will not work. You must create new ones that use a correct domain name URL. -
Give the generated token a name.
-
Parent topic: Creating a project