Image Customizations

Add additional jars

Adding additional jars to Keycloak’s deployment is as simple as adding that jar to the src/extra-jars directory.

Adding new jars will require building a new identity-config image for uds-core.

See Testing custom image in UDS Core for building, publishing, and using the new image with uds-core.

Once uds-core has sucessfully deployed with your new image, viewing the Keycloak pod can provide insight into a successful deployment or not. Also describing the Keycloak pod, should display your new image being pulled instead of the default image defined here in the events section.

Customizing Theme

Official Theming Docs

• Official Keycloak Theme Docs
• Official Keycloak Theme Github

For other changes beyond these images you will need to build a custom theme and identity-config image. Changes can be made to the src/theme directory. At this time only Account and Login themes are included, but email, admin, and welcome themes could be added as well.

Branding Customizations

The UDS Identity Config supports a limited and opinionated set of branding customizations. This includes:

• Changing the logo
• Changing the footer image
• Changing the favicon
• Changing the background image

These customizations require overriding the Keycloak Helm Chart provided by the UDS Core. Here’s an example:

packages:
  - name: core
    repository: oci://ghcr.io/defenseunicorns/packages/uds/core
    ref: x.x.x
    overrides:
      keycloak:
        keycloak:
          values:
            - path: themeCustomizations
              value:
                resources:
                  images:
                    - name: background.png
                      configmap:
                       name: keycloak-theme-overrides
                    - name: logo.png
                      configmap:
                        name: keycloak-theme-overrides
                    - name: footer.png
                      configmap:
                        name: keycloak-theme-overrides
                    - name: favicon.png
                      configmap:
                        name: keycloak-theme-overrides

The configuration supports four keys for different images: background.png, logo.png, footer.png, and favicon.png. You can set any or all of these images (you do not have to override all of them), and the corresponding key(s) must exist in your designated ConfigMap(s). Note that you must pre-create this ConfigMap in the keycloak namespace before deploying/upgrading Core with these overrides. In the above example all images are in the same ConfigMap named keycloak-theme-overrides. An easy way to generate the ConfigMap manifest is using the following command (including whichever images you need and specifying the correct paths to your local images):

kubectl create configmap keycloak-theme-overrides \
  --from-file=background.png=path/to/local/directory/background.png \
  --from-file=logo.png=path/to/local/directory/logo.png \
  --from-file=footer.png=path/to/local/directory/footer.png \
  --from-file=favicon.png=path/to/local/directory/favicon.png \
  -n keycloak --dry-run=client -o=yaml > theme-image-cm.yaml

To deploy this it is easiest to make a small zarf package referencing the manifest you just created:

kind: ZarfPackageConfig
metadata:
  name: keycloak-theme-overrides
  version: 0.1.0

components:
  - name: keycloak-theme-overrides
    required: true
    manifests:
      - name: configmap
        namespace: keycloak # Ensure this is in the Keycloak namespace
        files:
          - theme-image-cm.yaml # Update to the manifest you have locally

Then create and deploy this zarf package prior to deploying/upgrading UDS Core/Keycloak.

Terms and Conditions Customizations

In a similar theme to Branding customizations, the UDS Identity Config supports adjusting the Terms and Conditions (if enabled).

These customizations similarly require overriding the Keycloak Helm Chart provided by the UDS Core. Here’s an example:

packages:
  - name: core
    repository: oci://ghcr.io/defenseunicorns/packages/uds/core
    ref: x.x.x
    overrides:
      keycloak:
        keycloak:
          values:
            - path: themeCustomizations
              value:
                termsAndConditions:
                  text:
                    configmap:
                      key: text
                      name: keycloak-theme-overrides

The configuration supports a single key (named however you want) which must exist in the corresponding ConfigMap(s). Note that you must pre-create this ConfigMap in the keycloak namespace before deploying/upgrading Core with these overrides. The contents of this key must be your custom Terms and Conditions content, formatted as a single line HTML string. As a basic example you might want some terms and conditions like the following HTML:

<h4>By logging in you agree to the following:</h4>
<ul>
  <li>Terms</li>
  <li>And</li>
  <li>Conditions</li>
</ul>

In order to properly format this you will need to replace any newlines with the literal newline character (\n), converting your HTML to a single line. Using the above example that would look like this (again note the use of \n in place of the newlines):

<h4>By logging in you agree to the following:</h4>\n<ul>\n<li>Terms</li>\n<li>And</li>\n<li>Conditions</li>\n</ul>

Tip

This replacement process can easily be done with a tool like sed:

# This will require GNU sed
cat terms.html | sed ':a;N;$!ba;s/\n/\\n/g' > single-line.html

Your new single-line HTML file can be used to generate a properly formatted ConfigMap with the following command:

kubectl create configmap keycloak-theme-overrides \
  --from-file=text=path/to/local/directory/single-line.html \
  -n keycloak --dry-run=client -o=yaml > terms-and-confitions-cm.yaml

To deploy this it is easiest to make a small zarf package referencing the manifest you just created:

kind: ZarfPackageConfig
metadata:
  name: keycloak-terms-and-conditions
  version: 0.1.0

components:
  - name: keycloak-terms-and-conditions
    required: true
    manifests:
      - name: configmap
        namespace: keycloak # Ensure this is in the Keycloak namespace
        files:
          - terms-and-confitions-cm.yaml # Update to the manifest you have locally

Then create and deploy this zarf package prior to deploying/upgrading UDS Core/Keycloak.

Tip

In order to speed up the development process of the Customized Terms and Conditions, you can edit the ConfigMap in your cluster and then cycle the Keycloak pod to reload your updated Terms and Conditions. This will allow you to see the changes quicker without needing to rebuild/redeploy each time.

Note

The default terms and conditions provided are based on the standard DoD Notice and Consent Banner. The source HTML for these terms is in the identity-config repository here and could be used as a starting point for customizing. Note that you will need to follow the above steps to properly format this as single-line HTML and create a ConfigMap with its contents. There are some limitations and you won’t be able to dynamically lookup resources (i.e. ${url.resourcesPath}) due to the way this input is dynamically injected into the terms template so keep this in mind if trying to reference external images.

Registration Form Fields

Registration Form Fields, which by default are enabled, can be disabled to minimize the steps to register a new user. See this section for the example of disabling the registration form fields with the themeCustomizations.settings.enableRegistrationFields environment variable.

When disabled, the following fields will not be present during registration:

• Affiliation
• Pay Grade
• Unit, Organization or Company Name

Testing Changes

To test the identity-config theme changes, a local running Keycloak instance is required.

Don’t have a local Keycloak instance? The simplest testing path is utilizing uds-core, specifically the dev-identity task. This will create a k3d cluster with Istio, Pepr, Keycloak, and Authservice.

Once that cluster is up and healthy and after making theme changes, utilize this task to :

1. Execute this command:

      uds run dev-theme

2. View the changes in the browser

Customizing Realm

The UDS Identity realm is defined in the realm.json found in src/realm.json. This can be modified and will require a new uds-identity-config image for uds-core.

Note

Be aware that changing values in the realm may also need to be updated throughout the configuration of Keycloak and Authservice in uds-core. For example, changing the realm name will break a few different things within Keycloak unless those values are changed in uds-core as well.

See the Testing custom image in UDS Core for building, publishing, and using the new image with uds-core.

Templated Realm Values

Keycloak supports using environment variables within the realm configuration, see docs.

These environment variables have default values set in the realm.json that uses the following syntax:

  ${REALM_GOOGLE_IDP_ENABLED:false}

In the uds-core keycloak values.yaml, the realmInitEnv defines set of environment variables that can be used to configure the realm different from default values.

These environment variables will be created with a prefix REALM_ to avoid collisions with keycloak environment variables. If necessary to add additional template variables within the realm.json must be prefixed with REALM_.

For example, this bundle override contains all the available overrides:

overrides:
  keycloak:
    keycloak:
      values:
        - path: realmInitEnv
          value:
            GOOGLE_IDP_ENABLED: true
            GOOGLE_IDP_ID: <fill in value here>
            GOOGLE_IDP_SIGNING_CERT: <fill in value here>
            GOOGLE_IDP_NAME_ID_FORMAT: <fill in value here>
            GOOGLE_IDP_CORE_ENTITY_ID: <fill in value here>
            GOOGLE_IDP_ADMIN_GROUP: <fill in value here>
            GOOGLE_IDP_AUDITOR_GROUP: <fill in value here>
            EMAIL_VERIFICATION_ENABLED: true
            TERMS_AND_CONDITIONS_ENABLED: true
            PASSWORD_POLICY: <fill in value here>
            X509_OCSP_FAIL_OPEN: true
            ACCESS_TOKEN_LIFESPAN: 600
            SSO_SESSION_LIFESPAN_TIMEOUT: 1200
            SSO_SESSION_MAX_LIFESPAN: 36000
        - path: realmAuthFlows
          value:
            USERNAME_PASSWORD_AUTH_ENABLED: true
            X509_AUTH_ENABLED: true
            SOCIAL_AUTH_ENABLED: true
            OTP_ENABLED: true
            WEBAUTHN_ENABLED: true
            X509_MFA_ENABLED: true
        - path: themeCustomizations.settings
          value:
            enableRegistrationFields: true

These environment variables can be found in the realm.json.

Note

Important: By allowing certificates to pass when no revocation check is performed, you accept the risk of potentially allowing revoked certificates to authenticate. This can pose a significant security threat depending on your organization’s compliance requirements and threat model.

• Fail-Closed (X509_OCSP_FAIL_OPEN:false): More secure (no unchecked certificates) but can disrupt logins if the OCSP responder is unreachable.
• Fail-Open (X509_OCSP_FAIL_OPEN:true): More forgiving (users still log in if checks fail) but can allow revoked certificates if the OCSP server is down.

Customizing Session and Access Token Timeouts

The SSO_SESSION_IDLE_TIMEOUT specifies how long a session remains active without user activity, while the ACCESS_TOKEN_LIFESPAN defines the validity duration of an access token before it requires refreshing. The SSO_SESSION_MAX_LIFESPAN determines the maximum duration a session can remain active, regardless of user activity.

To ensure smooth session management, configure the idle timeout to be longer than the access token lifespan (e.g., 10 minutes idle, 5 minutes lifespan) so tokens can be refreshed before the session expires, and ensure the max lifespan is set appropriately (e.g., 8 hours) to enforce session limits. Misalignment, such as setting a longer token lifespan than the idle timeout or not aligning the max lifespan with session requirements, can result in sessions ending unexpectedly or persisting longer than intended.