Configuration Overview
On this page
When you onboard to the Curity Identity Server, you need to understand how to manage state and deploy the Curity Identity Server. One type of state is identity data like user accounts, credentials, sessions and tokens that you need to manage using database storage. First though, you should understand how to manage configuration, which is the subject of this tutorial.
The Curity Identity Server is a cloud native product, and deployment itself requires only a simple operation like running a Docker container. If you are using an orchestration platform like Kubernetes, you don't even have to do that. Instead, you simply express your desired state and the platform takes care of deployment for you.
Configuration Management System
The key to managing deployment, high availability and upgrades well is effective configuration management. Whether you are using the full Curity Identity Server or the Standalone Token Handler, the system you deploy has strong configuration support:
| Feature | Behaviors |
|---|---|
| Configuration as Code | You manage your configuration in source control |
| Protected Secrets | You store secrets in a secure vault and protect secure values at deployment time |
| Parameterized | You parameterize configuration to avoid duplication in your deployment pipeline |
| Modular | You modularize your configuration to keep it maintainable |
| Reliable | The configuration system is transactional and you can rollback to your last good configuration |
| Flexible | Your configuration can express our deployment concepts to enable flexible rollouts |
Learning Configuration
First, familiarize yourself with the basic usage of configuration. Learn how to use the admin UI to make configuration changes, then back them up:
Next, understand how to manage configuration for your deployed environments. By treating configuration as code you can store many security-related settings in source control or a secure vault and minimize duplication.
Finally, read specific configuration tutorials on topics like the Command Line Interface (CLI) and Keys, Certificates and Trust Stores. You can also consult the Detailed Configuration Guide.
Reliable Deployments
Once you know how to configure the Curity Identity Server, deploy the same standardized machine image and parameterized configuration to all stages of your deployment pipeline. Doing so avoids duplication of security settings and takes the pain out of production upgrades.
Conclusion
Configuration management and deployment are closely related. When operating a critical component like an authorization server, you should consider a solid configuration management design to be essential. When onboarding to the Curity Identity Server, you have many tools and techniques to help you on your journey.
Join our Newsletter
Get the latest on identity management, API Security and authentication straight to your inbox.
Start Free Trial
Try the Curity Identity Server for Free. Get up and running in 10 minutes.
Start Free Trial
