Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Automator 18.0.0

Released on October 29, 2026

This is a major, security-focused release of Keeper Automator. It adds cryptographic verification of every request sent from Keeper to Automator, per-configuration encryption keys, and support for running the Automator container as a non-root user. All Automator deployments should be upgraded to version 18.0.0 as soon as possible, or during the next scheduled maintenance window.

New Features

  • KAA-191: Optional non-root container operation. The Automator Docker image now includes a dedicated automator account (UID/GID 10001:10001), so customers can choose to run the JVM as a non-root user. The image still runs as root by default, so existing deployments can upgrade without changing their user, port, or storage configuration. An optional docker-compose.nonroot.yml override is now included in the distribution ZIP. See "Running Automator as a non-root user (optional)" below.

Improvements

  • KAA-188: Thread-safe endpoints. Automator endpoints now handle concurrent requests safely.

  • KAA-197: Clearer permission logging. Logging now states clearly when a non-root Automator process cannot read a root-owned configuration folder, which makes permission problems easier to diagnose.

  • KAA-199: Smaller base image. The musl-utils and java-common packages have been removed from the Alpine base image.

Security Updates

  • KAA-183: Keeper request signature verification. Automator now verifies that every incoming request, on all endpoints except /health, was signed by Keeper. Verification uses a built-in Keeper public key and supports key rotation. Each request carries a signature, key ID, timestamp, and nonce. Requests that are unsigned, changed in transit, older than the allowed time window, or replayed are rejected. See "Request signature headers" below.

  • KAA-174: Per-configuration transmission keys. Each Automator configuration now gets its own unique AES transmission key, replacing the single key that was shared across the whole instance. Existing enrolled configurations are migrated automatically to keep their current key, so traffic is not interrupted. New configurations, including deleted and re-created ones, get a newly generated unique key.

  • KAA-193: Signed Automator ID enforcement. Automator endpoints now ignore any Automator ID in the request URL. They use only the ID inside the signed request.

  • KAA-187: Test mode hardening. Device approval endpoints can no longer switch Automator into test mode.

  • KAA-192 / KAA-196: Third-party library and container image updates. Library dependencies and native image packages have been upgraded according to our regular SDLC process. Docker image vulnerability scanning has been added to the release pipeline.

Critical Upgrade Instructions

1. Request signature headers

Starting with version 18.0.0, every request from Keeper to Automator includes the following headers:

  • X-Automator-Request-Signature

  • X-Automator-Request-Key-Id

  • X-Automator-Request-Timestamp

  • X-Automator-Request-Nonce

Passing requests through a reverse proxy

A reverse proxy, load balancer, or web application firewall between Keeper and Automator must pass all four headers and the request body without changing their values or contents. Removing a required header, replacing the signature, or changing data covered by the signature causes verification to fail.

Keeper and Automator must have accurate clocks so that requests remain within the 60-second window. Each retry must use a new nonce, a current timestamp, and a new signature. Resending a previously accepted request with the same headers is rejected while its nonce remains in the cache.

2. Running Automator as a non-root user (optional)

The Docker image defaults to root for compatibility. This section describes the opt-in non-root configuration for customers who want the JVM to run as UID/GID 10001:10001.

The non-root process needs write access to /usr/mybin/config to persist state and /usr/mybin/logs to write rolling logs. Packaged settings, libraries, and the application JAR remain root-owned and read-only.

Option 1: Keep the internal listener on port 443

Use NET_BIND_SERVICE to allow the non-root JVM to bind port 443. For direct Docker, a named config volume can be initialized and mounted as follows:

For Docker Compose, use the optional docker-compose.nonroot.yml override included in the distribution ZIP:

The override sets UID/GID 10001, drops all capabilities, adds NET_BIND_SERVICE, and runs a one-shot config-permissions service to initialize the named config volume before Automator starts.

For bind-mounted config directories, make the host path writable by UID/GID 10001 before starting the container:

If logs are also mounted from the host, update that directory too:

docker cp creates files in the container as root by default. For the direct Docker example above, stop Automator after copying the certificate files and use a temporary root helper against the mounted config volume to set ownership and private file permissions:

If a password file is used, include it in the helper command as well:

For Compose, restart the optional root-owned initializer after copying the files; it fixes ownership and sets the PFX/password file modes to 0600:

Verify the opt-in process identity and runtime directory permissions:

The process should report UID/GID 10001, and both runtime directories must be writable by that user.

Option 2: Capability-free fallback on port 8443

If the deployment platform cannot provide NET_BIND_SERVICE, the non-root JVM can listen on unprivileged port 8443. Change the internal/container target and AUTOMATOR_PORT; the public listener can remain on 443:

For Compose, set AUTOMATOR_PORT=8443 and map the existing host port to container port 8443, for example 8089:8443. Update backend targets and health probes to 8443 as well. Keep the public listener and Commander URL unchanged when the external port remains unchanged. Drop all capabilities; do not add NET_BIND_SERVICE for port 8443. If adapting the docker-compose.nonroot.yml override, remove its NET_BIND_SERVICE addition for this fallback.

Example Compose service settings (combine with the config-volume ownership initialization described above):

Kubernetes non-root deployment

Merge the following relevant fields into the existing Deployment and Service manifests. This example shows non-root binding port 443 with NET_BIND_SERVICE. For the capability-free fallback, set AUTOMATOR_PORT, containerPort, Service targetPort, and probe ports to 8443, and omit the NET_BIND_SERVICE addition. The Service's public port can remain 443. Keep the pod non-root and ensure its config volume is writable by UID/GID 10001:

Configure readiness/liveness probes to the selected container port. Check storage-driver behavior: fsGroup is not honored by every driver, and existing PVC contents may require a one-time ownership migration. Ensure certificate Secret files are readable by UID/GID 10001 without making private key material world-readable.

General Update Instructions

  • For container deployments, update the container and restart the service. Then run "automator setup" followed by "automator init" as described in the relevant section "Installation Method" for your type of deployment.

  • For other deployment methods, see the Automator documentation to update.

See the Keeper Automator Documentation for full deployment and configuration management instructions.

Last updated