EJBCA License

As of EJBCA 9.4, EJBCA container deployments require a valid license file to start and operate.

Reach out to Keyfactor by submitting a request via the Keyfactor Support Portal to obtain a valid license file prior to upgrading to EJBCA 9.4.

Apply a license file in EJBCA Container Set deployments

The EJBCA Helm chart enables you to provide the license file as a Kubernetes secret, allowing it to be managed and applied as part of your configuration.

To apply the license:

Create a Kubernetes secret in the appropriate namespace using your license file.
The file name inside the secret must be ejbca-license .
BASH
```
kubectl create secret generic ejbca-license-secret -n {NAMESPACE} \
  --from-file=ejbca-license=<license-file>
```
Reference the secret in your Helm values.yaml file:
YAML
```
...
ejbca:
  license: ejbca-license-secret
...
```

Once the license secret is configured, upgrade EJBCA as usual using the Helm chart:

BASH

helm upgrade <deployment-name> -f values.yaml \
  oci://repo.keyfactor.com/charts/ejbca --version 9.4.0

License File System Behavior

The table below summarizes the resulting system behavior in a deployed system based on the status of the EJBCA license file.

EJBCA License File Status	System Behavior
Valid License File	Normal operation
Invalid or Missing License File Missing Invalid file Unparseable license Invalid signature	EJBCA shuts down
Expiring License 60 days or less to expiry 30 days or less to expiry 5 days or less to expiry	Message in logs and Admin UI
Expired License Expired less than 90 days	Message in logs and Admin UI
Expired License Expired more than 90 days	EJBCA shuts down