Connecting an environment to Salto
To connect an Okta tenant (prod, sandbox, etc.), you will need to authenticate via Oauth or use an API token.
Detailed Okta environment setup instructions can be found here
Env settings
To update the settings for a particular environment, navigate to the settings section where you will find:
General: where to update the environment name, setup the Scheduled fetch, and optionally mark an environment as "sensitive"
Application Connections:
credentials used for fetch and deploy (Note: make sure you have set up "Personal credentials" in the environment ahead of starting a deployment).
Version Control: Git connection for the environment
Monitor changes: where to set up custom notifications (see below)
Impact Analysis
The explore page in Salto is used to explore your configurations, see dependencies and understand where and how configurations are used.
Monitoring changes
Set up notifications to alert when changes are made in production.
Comparison Overview (Compare & Deploy)
Here is an overview of the comparison screen showing you the differences between two environments, part of the compare and deploy process.
Backup and Restore
Through the scheduled fetch, Salto will automatically backup the configurations for each environment. Those backups can be used through the restore process to revert any changes made directly in the environment. 🎥 How to restore your Okta configuration to a previous version - 3min
Configuration issues and Environment alignment
When an environment is first connected to Salto, you may see a number of configuration issues, such as identically named elements or permissions issues.
Be aware that Salto uses the names of elements to align them between environments. For example, if a group is named "Employee" in sandbox and "Employees" in Production, Salto will see those as 2 separate groups, which could lead to unexpected misalignment issues.
Deployment types
There are different types of deployments in Salto
Compare & Deploy: Choose which changes to align between any two environments.
Find environment changes & deploy: Choose the changes made during a specific time period to deploy into another environment. Especially useful when deploying from a shared environment.
Promote a deployment: used to promote the same set up changes to another target environment. (ex: after deploying a set of updates to a form in
UAT, promoting those same changes up toProduction)Revert a deployment: Revert all changes made in a specific deployment (Note: to revert specific changes, use the restore process mentioned above)
Deployment example
Known Limitations
Support of Okta’s classic engine is available, yet limited and active work in progress. If you run into any issues, please reach out to us @ support@salto.io.
Application integration limitations:
Any app configuration changes done using Salto change only the Okta side. Additional setup might be needed in the integrated app.
Sharing application key credentials across multiple apps is not supported yet (Okta’s doc)
Okta Workflows are not supported.
Additional References