Automator Version 3.2

Released on Dec 8, 2023

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 Azure Container App deployment

• Support for simplified AWS ECS Service 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:

automator edit --skill=team --skill=team_for_user --skill=device "My Automator"
automator setup "My Automator"
automator init "My Automator"
automator enable "My Automator"

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:

services:
  automator:
    container_name: "az-autodock"
    environment:
      - AUTOMATOR_PORT=8090
      - AUTOMATOR_HOST=10.0.0.4
      - DISABLE_SNI_CHECK=true

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

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