Janssen
Services authenticate with the Janssen client they run as.
Services authenticate with the Janssen client they run as.
Identity proof
The token has to come from https://auth.acme.com, and its sub claim has to match the workload you named. We compare that claim byte for byte, with no wildcards.
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
| Field | Example | Advanced | What it pins |
|---|---|---|---|
| Janssen URL | https://auth.acme.com | no | The issuer your /.well-known/openid-configuration shows. Must be reachable from the internet. |
| Client ID | 2200.4b3c1a8e-7d2f-4e61-9c0b-5a8f3e2d1c7b | no | Admin UI → Clients → Client ID. Every machine holding its secret matches. |
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:
| What | Value |
|---|---|
| Issuer | https://auth.acme.com |
| Claim compared | sub |
| Subject | 2200.4b3c1a8e-7d2f-4e61-9c0b-5a8f3e2d1c7b |
| Identity name | janssen-5a8f3e2d1c7b |
We name the identity for you, so the form never asks for one.
Console snippet
# Janssen client, once: access token as JWT, grant type client_credentials only,
# subject type public, token endpoint auth method client_secret_post, signing alg RS256.
# An UpdateToken script enabled on the client, with its client id in place of <CLIENT_ID>:
# def modifyAccessToken(self, accessToken, context):
# grant = context.getGrant()
# if grant.getClientId() == "<CLIENT_ID>" and grant.getAuthorizationGrantType().toString() == "client_credentials":
# context.getClaims().setClaim("aud", "YOUR_WORKSPACE_ID")
# return True
# Ask for this audience and no other. A token requested for two audiences fails every exchange.
# $JANS_CLIENT_ID and $JANS_CLIENT_SECRET are this client's own, already on the machine.
URL=$(curl -fsS "<JANSSEN_URL>/.well-known/openid-configuration" | jq -r .token_endpoint)
T=$(jq -jn \
'"grant_type=client_credentials&client_id=\((env.JANS_CLIENT_ID // "" | if . == "" then error("JANS_CLIENT_ID is not set") else . end)|@uri)&client_secret=\((env.JANS_CLIENT_SECRET // "" | if . == "" then error("JANS_CLIENT_SECRET is not set") else . end)|@uri)"' \
| curl -fsS "$URL" --data-binary @- | jq -r .access_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 pullThe 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
- Janssen documentation: the subject is the value most often set wrong