9.6.2-7.8 9.6.2-7.7 9.6.1-7.7 9.5-7.6 9.4.2-7.5 9.3.6-7.4 9.3.5-7.4 9.3.4-7.4 9.3.3-7.3.2 9.3.2-7.3.2 EJBCA SignServer
9.6.2-7.8 9.6.2-7.7 9.6.1-7.7 9.5-7.6 9.4.2-7.5 9.3.6-7.4 9.3.5-7.4 9.3.4-7.4 9.3.3-7.3.2 9.3.2-7.3.2 EJBCA SignServer

Restrict EJBCA Access to HTTPS (TLS)

For enhanced security, you can restrict EJBCA access by enforcing HTTPS (TLS) and disabling plain HTTP.

Below are example configurations to configure HTTPS-only access by updating the corresponding values.yaml file.

Using Ingress

Add the following configurations to the values.yaml:

YAML
# set services.proxyHttp.httpPort to empty value
services:
  proxyHttp:
    httpPort:

# enforce ssl-redirect at ingress
ingress:
  enabled: true
  annotations:
    nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
  # other mandatory configurations are omitted for brevity

Using LoadBalancer

Add the following configurations to the values.yaml:

YAML
# set nginx.service.httpPort to empty value
nginx:
  enabled: true
  service:
    type: LoadBalancer
    httpPort:
  # other mandatory configurations are omitted for brevity

# set services.proxyHttp.httpPort to empty value
services:
  proxyHttp:
    httpPort:


With these configurations, EJBCA access is restricted to only HTTPS.