Overview

Version 3.2 incorporates Team approvals on top of the 3.1 capabilities. In summary, version 3.2 incorporates the below new features:

• Team Approval and Creation (new for 3.2)

• Team User Approvals

• All settings can be configured as environment variables

• Support for simplified deployment

• Support for simplified deployment

• HSTS is enabled for improved HTTPS security

• IP address filtering for device approval and team approval

• Optional rate limiting for all APIs

• Optional filtering by email domain

Team Approval and Team User Approvals

Teams that are provisioned through SCIM can be immediately processed by the Automator service (instead of waiting for the admin to login to the console).

To activate this new feature:

• Update your Automator container to the latest version

• Use the automator edit command in Keeper Commander to instruct the service to perform team and team user approvals:

All settings can be configured as environment variables

This makes configuration easier when installing Automator in Azure Containers or other Docker-like containers where access to the settings file is difficult.

In Docker, Azure Containers, or other environments that use the docker-compose.yml file, you can set environment variables in the docker compose file, for example:

After editing the docker-compose.yml file, you will need to rebuild the container if the environment variables have changed. Just restarting the container will not incorporate the changes.

Advanced Features

for all of the new and advanced features / settings for the Automator service.

Overview

Version 17.0.0 features the following improvements and fixes below:

• KAA-78: Support for RSA to EC migration

• KAA-80: Automator will enforce EC-only restrictions as directed by the backend

• KAA-45: Upgrade BouncyCastle library to FIPS version

• KAA-97: Upgraded Jetty to v12

Update Instructions

• For container deployments, simply update the container and restart the service

• For other deployment methods, see the to update

Advanced Features

for all of the new and advanced features / settings for the Automator service.

Overview

Version 3.2.1 features the following improvements and fixes below:

• KAA-88: Update dependent libraries

• KAA-93: RSA public-private key format fix to prevent team approval failure via Automator

• KAA-89: Enable HTTPS correctly when SSL_CERTIFICATE environment variable is used

• KAA-85: Increase rate limit on health check

• KAA-94: Fix restore configuration from Keeper Cloud during Automator restarts

Update Instructions

• For container deployments, simply update the container and restart the service

• For other deployment methods, see the to update

Advanced Features

for all of the new and advanced features / settings for the Automator service.

Bug Fixes

• KAA-64: Automator fails with invalid_signing_key if there are 2 different signing keys in the Identity Provider metadata

• KAA-63: Disabling SNI check is not working properly.

Initial customer release of Keeper Automator

Automator Version 1.0.4 contains a security update that is recommended for all customers.

Please contact Keeper Enterprise support if you require assistance with the upgrade.

For update instructions, see the below link:

Overview

Automator Version 2.1 is a major upgrade of the Keeper Automator service.

• Automatic configuration reload on service restart

• Docker and Docker Compose install methods

• New Windows Service installer

• MSP multi-tenant configuration for Managed Companies

Upgrade from 1.x to 2.1

A direct path to upgrade is not available. Installing a fresh new version of the Automator is the recommended path forward.

Upgrade Instructions:

(1) From Commander, disable the current automator:

(2) Retrieve the ssl-certificate.pfx and ssl-certificate-password.txt files from your current installation of Automator. If no password is set for the certificate, you only need the ssl-certificate.pfx file.

(3) Install a new version of Automator using one of the new installation methods:

(4) Run the setup/init/enable commands from Commander:

New Features

• KAA-28: Support approvals for multiple MCs within the same tenant For more information see .

• KAA-41: Support for conditional approvals based on a new SAML response flag DeviceApprovalRequired which can be set to true or false. A value of "true" means that the device needs to be manually approved by the user. A value of "false" means that the device should be automatically approved by the automator service.

Changes and Improvements

• KAA-59: The default port listener has been changed to 443 (instead of 8089) for compatibility with Azure Container Service deployment method.

Automator Version 1.0.5 contains a security update that is recommended for all customers.

Please contact Keeper Enterprise support if you require assistance with the upgrade.

For update instructions, see the below link:

Version 1.0.6 supports Windows Services. To convert an existing Windows cmd-line install to the full Services mode, follow the steps below:

• Stop the existing service

• Unzip and Install the new Automator: https://keepersecurity.com/automator/keeper-automator-windows.zip

• Copy the contents of the old Automator properties/ folder from the old location to C:\ProgramData\Keeper Automator\settings\

• Open Windows Services

• Start the Keeper Automator service

• From Commander, run "automator setup", "automator init" and "automator enable" as normally would be done.

Overview

Version 3.1 incorporated several new features:

• Team User Approvals

• All settings can be configured as environment variables

• Support for simplified deployment

• Support for simplified deployment

• HSTS is enabled for improved HTTPS security

• IP address filtering for device approval and team approval

• Optional rate limiting for all APIs

• Optional filtering by email domain

Team User approvals

Version 3.x introduced Team User approvals. This means that users who are provisioned through SCIM and added to teams can be immediately processed by the Automator service (instead of waiting for the admin to login to the console).

To activate this new feature:

• Update your Automator container to the latest version

• Use the automator edit command in Keeper Commander to instruct the service to perform device approvals and also perform Team User approvals:

Example:

All settings can be configured as environment variables

This makes configuration easier when installing Automator in Azure Containers or other Docker-like containers where access to the settings file is difficult.

In Docker, Azure Containers, or other environments that use the docker-compose.yml file, you can set environment variables in the docker compose file, for example:

After editing the docker-compose.yml file, you will need to rebuild the container if the environment variables have changed. Just restarting the container will not incorporate the changes.

Advanced Features

for all of the new and advanced features / settings for the Automator service.