Manage Token Issuer Allow/Deny Lists
The Platform Management Service can be configured with INRUPT_JWT_ISSUER_ALLOW_LIST and INRUPT_JWT_ISSUER_DENY_LIST to manage which external Identity Providers are trusted to issue tokens that can be exchanged for ESS Access Tokens.
How the Lists Work
If
INRUPT_JWT_ISSUER_ALLOW_LISTis set, the Platform service only accepts tokens from issuers in the list (subject to the deny list).If
INRUPT_JWT_ISSUER_ALLOW_LISTis unset, the Platform service accepts tokens from all issuers (subject to the deny list).If
INRUPT_JWT_ISSUER_DENY_LISTis set, the Platform service rejects tokens from those issuers, even if they appear in the allow list. The deny list always takes precedence.
Example: Update INRUPT_JWT_ISSUER_ALLOW_LIST
To restrict the Platform service to only accept tokens from specific Identity Providers:
Go to your ESS installation directory:
cd ${HOME}/essModify the
kustomization.yaml(i.e., step 3 of the Applying Your Customizations procedure). Specifically, add the highlighted content to thekustomization.yamlfile to thepatchessection:# kustomization.yaml in your ESS installation directory # ... Preceding content omitted for brevity # ... patches: - target: kind: Deployment name: ess-platform-management patch: | - op: add path: /spec/template/spec/containers/0/env/- value: name: INRUPT_JWT_ISSUER_ALLOW_LIST value: "https://login.example.com,https://accounts.google.com"Continue with the rest of the Applying Your Customizations procedure.
Example: Update INRUPT_JWT_ISSUER_DENY_LIST
To block specific Identity Providers from being used for token exchange:
Go to your ESS installation directory:
Modify the
kustomization.yaml(i.e., step 3 of the Applying Your Customizations procedure). Specifically, add the highlighted content to thekustomization.yamlfile to thepatchessection:Continue with the rest of the Applying Your Customizations procedure.
Last updated