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

# Automator Version 17.1.2

This is a security-focused release addressing several 3rd party penetration testing reports and library depedencies. All Automator deployments should be upgraded to version 17.1.2 as soon as possible, or during the next scheduled maintenance window.

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

### Security Updates

* **KAA-167: Deserialization Hardening**\
  Applied a strict ObjectInputFilter allow-list to Java deserialization paths, blocking untrusted classes from being instantiated during object deserialization. Only explicitly permitted packages (Keeper, Protobuf, BouncyCastle, Keycloak, and a minimal set of JDK primitives/collections) are now accepted.
* **KAA-167: Path Traversal Protection**\
  SSL password file path configuration now canonicalizes the resolved path and rejects any path that resolves outside the Automator working directory, preventing directory traversal attacks against local file resources.
* **3rd party library dependencies**: We have upgraded 47 library dependencies in accordance to our regular SDLC process.

### Update Instructions

{% hint style="warning" %}
Updating to version 17.1.2 requires a re-initialization due to encryption changes
{% endhint %}

* For container deployments, update the container and restart the service. Then run "**automator setup**" followed by "**automator init**" as described in the [relevant section](/sso-connect-cloud/device-approvals/automator.md#installation-options) "Installation Method" for your type of deployment.
* For other deployment methods, see the [Automator documentation](/sso-connect-cloud/device-approvals/automator.md) to update

### Advanced Features

[See this page](/sso-connect-cloud/device-approvals/automator/advanced-settings.md) for all of the new and advanced features / settings for the Automator service.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.keeper.io/release-notes/developer-tools/automator/automator-version-17.1.2.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.