Domino v5.3.0 & v5.3.1
Kerberos enabled workspaces fail to start with the following error:
java.lang.IllegalStateException: DOMINO_KERBEROS_KEYTAB_FILE_CONTENT_FOR_USER environment variable not defined
Domino changed the way environment variables are implemented in v5.3.0+, reading them from the secret vault. Kerberos expects the environment variable noted in the error, DOMINO_KERBEROS_KEYTAB_FILE_CONTENT_FOR_USER, to already be available within the execution on startup.
This issue has been resolved in Domino v5.3.2 and beyond. If you need a mitigation until you reach that version of Domino, apply the following workaround.
Set the Central Config key:
to a value of
and restart nucleus services.
If your deployment does not have direct access to quay.io, then you will need to pull this image to your internal image repository and update the image location to point to your internal address.