> For the complete documentation index, see [llms.txt](https://newdocs.keeper.io/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://newdocs.keeper.io/en/release-notes/developer-tools/automator/automator-version-17.1.4.md).

# Automator 17.1.4

Released on August 26, 2026

This is a security-focused release based on 3rd party security pen testing. All Automator deployments should be upgraded to version 17.1.4 as soon as possible, or during the next scheduled maintenance window.

As documented, ensure all Automator deployments adhere to our recommended [Ingress Requirements](/en/sso-connect-cloud/device-approvals/automator/ingress-requirements.md), ensuring all inbound traffic is restricted to Keeper's infrastructure.

### Security Updates

* KAA-180: Security Updates based on 3rd party vulnerability testing

### Important Upgrade Information

Updating your Automator from older releases (such as 17.1.0 or 17.1.1) may require a setup and re-initialization step.

**For Container Deployments:** Update the container image to `17.1.4` and restart the service. If upgrading from a previous release containing legacy serialized configuration data, run `automator setup <automator-id>` followed by `automator init <automator-id>` via Commander CLI as described in the deployment documentation.

**For Non-Container Deployments:** Refer to the Keeper Automator documentation to update service binaries and execute `automator setup` / `automator init` from Commander CLI, if required.

See the [Keeper Automator Documentation](/en/sso-connect-cloud/device-approvals/automator.md) for full deployment and configuration management instructions.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://newdocs.keeper.io/en/release-notes/developer-tools/automator/automator-version-17.1.4.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.