Set Authorization Client Allow List

The Authorization Service uses its INRUPT_AUTHORIZATION_CLIENT_ID_ALLOW_LIST option to specify which applications can access Access Control Resources (ACRs) . Only the clients associated with the Client IDs in the list can modify the ACRs (i.e., modify access policies for resources).

Example Customization

The following customization updates:

  1. Go to your ESS installation directory:

    cd ${HOME}/ess
  2. Create a authz-client-id-allow-list.yaml file with the following content:

    apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: ess-authorization-acp
    spec:
      template:
        spec:
          containers:
          - env:
            - name: INRUPT_AUTHORIZATION_CLIENT_ID_ALLOW_LIST
              value: https://myApp.example.com/appid
            name: ess-authorization-acp
  3. Create a podconfig-client-id-allow-list.yaml file with the following content:

    apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: ess-pod-storage
    spec:
      template:
        spec:
          containers:
          - env:
            - name: INRUPT_AUTHORIZATION_CLIENT_ID_ALLOW_LIST
              value: https://myApp.example.com/appid
            name: ess-pod-storage
  4. Modify the kustomization.yaml (i.e., step 3 of the Applying Your Customizations procedure) to use authz-client-id-allow-list.yaml and podconfig-client-id-allow-list.yaml . Specifically, add the highlighted content to the kustomization.yaml file to the patches section:

Tip

If the patches key does not exist in kustomization.yaml , add the key patches as well.

<pre class="language-yaml"><code class="lang-yaml">
# kustomization.yaml in your ESS installation directory
# ...  Preceding content omitted for brevity 
# ...
patches:
<strong>  - path: authz-client-id-allow-list.yaml
  - path: podconfig-client-id-allow-list.yaml
</strong>
</code></pre>
  1. Continue with the rest of the Applying Your Customizations procedure.

Last updated