Automated SecureAuth Configuration Management
Automate management of SecureAuth configuration - promote changes between different types of environments, and more.
Note
Test use only. Subject to potential functionality limitations, breaking changes, future updates, and removal without notice.
Why Automate Configuration Management
There are myriad reasons to automate the management of your IT infrastructure. Your SecureAuth is no exception. Here are just some of the key reasons you should consider automating your configuration management:
Consistency and Standardization: Automation ensures that all tenants and workspaces are configured consistently, following standardized configurations.
Scalability: As your SecureAuth configuration grows, manual configuration becomes increasingly challenging and time-consuming. Automation provides reassurance that you have a consistent, exact configuration across all your potential tenants/workspaces.
Reduced Human Errors: Manual configurations are prone to human errors. Automated configuration management promotes necessary changes to higher-level tenants and removes manual configurations, reducing potential security vulnerabilities in the long term.
Rapid Provisioning: Automated configuration allows for quick and repeatable provisioning of tenants and workspaces. The timeline between a configuration update and deployment in a production tenant/workspace can be reduced drastically.
Version Control and Auditing: Configuration export files and templates can be version-controlled, enabling easy rollbacks and change tracking. This provides better visibility and auditability of configuration changes.
Automated configuration management has become a crucial component for modern dev-ops and site-reliability engineers. The management of your SecureAuth should not be an exception!
Configuration APIs
The SecureAuth configuration APIs , are a critical component in automating your SecureAuth configuration. The can be used to establish the export and patching functionality required to promote configurations across tenants and workspaces.
The SecureAuth configuration APIs utilize a JSON tree structure that is easy to read and manage by implementing the JSON Merge Patch RFC 7396 specification.
JSON Patch Tool
The other key component for enabling the automation of your SecureAuth configuration, is a tool for creating JSON Patch documents - based on your tenants/workspaces configuration.
This tool should create appropriate JSON Patch documents (adhering to RFC 7396 or RFC 6902 ) from the output of the new SecureAuth configuration Export APIs.
The resulting JSON Patch document can then be used as input to the SecureAuth configuration Patch APIs.
For customers with intricate configurations and specific requirements, it may be necessary to develop custom JSON Patch Tools. SecureAuth has developed a tool that serves as an example for simpler use cases and provides a foundation for tackling more complex scenarios.
For an example JSON Patch Tool written in Go and using GitHub Actions, see our GitHub repo.
What's Next
If you have made it to this point, you clearly have a need to automate your SecureAuth configuration and are ready to get started. So, where to go from here?
For starters, you could take a look at the related articles. If you haven't already read them, they should provide additional details about the suggestions/solutions provided by SecureAuth.