Comment on page
Automator Version 3.1
Released on November 2, 2023
Version 3.1 incorporated several new features:
- Team User Approvals
- All settings can be configured as environment variables
- 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
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 editcommand in Keeper Commander to instruct the service to perform device approvals and also perform Team User approvals:
Example:
automator edit --skill=team_for_user --skill=device "My Automator"
automator setup "My Automator"
automator init "My Automator"
automator enable "My Automator"
Team approvals are coming in version 3.2. This current version only performs team user assignments.
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.Last modified 30d ago