> 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.1.md).

# Automator Version 17.1.1

### Improvements

* The `keeper-automator.jar` file is now minimized — unused classes have been removed, resulting in a smaller deployment footprint and faster startup time.
* Windows build hardened: ensures the `build\wix` directory exists before running heat, and the `automator_heat.bat` script is more robust against edge-case failures.

### Security Updates

* Addressed Bugcrowd reported vulnerabilities.
* Upgraded transitive Netty dependency to remediate a flagged CVE.
* Mitigated multiple library-related CVEs through updated dependencies and Dockerfile hardening.
* Fixed additional vulnerabilities identified by Manifest security scanning.
* Eliminated MavenGate supply-chain exposure by building exclusively from libraries hosted in Keeper Central.
* Automator now rejects `setup_crypto` step 1 requests when the service is already in a RUNNING state, preventing potential misconfiguration during active operation.

### Bug Fixes

* Fixed an issue where team approvals were sending incorrect information, causing users not to be added to Teams after Automator approved the operation.

### Update Instructions

* For container deployments, simply update the container and restart the service
* 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.1.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.