The Step fetches an OIDC identity token.
Description
The Step fetches an OIDC identity token.
The token can be used to authenticate with services that support OIDC tokens, such as Google Cloud, AWS, Azure or others. This allows secure, token-based authentication without the need to manage long-lived credentials.
Add this step directly to your workflow in the Bitrise Workflow Editor.
You can also run this step directly with Bitrise CLI.
Inputs
| Key | Description | Flags | Default |
|---|---|---|---|
audience |
The audience for the identity token. This could be the URL of the service you want to access with the token or a specific identifier provided by the service. | required | |
build_url |
Unique build URL of this build on Bitrise.io. By default the step will use the Bitrise API. | required | $BITRISE_BUILD_URL |
build_api_token |
The build's API Token for the build on Bitrise.io This will be used to communicate with the Bitrise API | required, sensitive | $BITRISE_BUILD_API_TOKEN |
verbose |
Enable logging additional information for debugging. | required | false |
Outputs
| Environment Variable | Description |
|---|---|
BITRISE_IDENTITY_TOKEN |
The newly generated identity token. |
We welcome pull requests and issues against this repository.
For pull requests, work on your changes in a forked repository and use the Bitrise CLI to run step tests locally.
Note: this step's end-to-end tests (defined in e2e/bitrise.yml) are working with secrets which are intentionally not stored in this repo. External contributors won't be able to run those tests. Don't worry, if you open a PR with your contribution, we will help with running tests and make sure that they pass.
Learn more about developing steps: