Bitbucket Pipelines

Steps authenticate as the repository they ran in.

Identity proof

The token has to come from https://api.bitbucket.org/2.0/workspaces/acme/pipelines-config/identity/oidc, and its repositoryUuid claim has to match the workload you named. We compare that claim byte for byte, with no wildcards.

repositoryUuid is matched rather than sub, which on this platform does not name the workload in a form you can pin.

Every token also has to name your workspace as its audience. Ask for this audience and no other. A token requested for two audiences fails every exchange.

Console fields

The console also asks which project and environment this identity reaches and which role it gets, with the credential lifetime behind Advanced.

Trust

Built from the example answers above:

We name the identity for you, so the form never asks for one.

Console snippet

pipelines:
  default:
    - step:
        oidc:
          audiences:
            - YOUR_WORKSPACE_ID
        script:
          - |
            T="$BITBUCKET_STEP_OIDC_TOKEN"
            C=$(T="$T" jq -n '{token:env.T}' | curl -sS "https://penv.cloud/api/v1/auth/oidc" \
              -H 'content-type: application/json' --data-binary @- | jq -r .credential)
            PENV_TOKEN="$C" penv pull

The snippet finishes with penv pull, which writes a file. We recommend penv run for a process; penv pull is for a host that needs a file on disk. Connect your CI has the wrapped step.

Related

• Machine identity
• Connect a Platform in the console
• Bitbucket Pipelines documentation: the subject is the value most often set wrong