Automated configuration and management has been the holy grail of network management for many years. The identity sphere has not caught on, until now.
Using Curity means safe and controlled changes with transactional updates of configuration, revision history and rollback capabilities. All configuration in Curity can be managed manually or programmatically, using: Command Line Interface (CLI), REST API or Web User Interface.
Curity has a built in web user interface that can be reached on the admin node. It can be used to control the cluster, or as a standalone tool to prepare new configurations that can be downloaded as XML and pushed out at a later stage.
Curity comes with one of the most advanced command line interfaces (CLI) on the market. With a complete Juniper styled CLI the dev-ops team can login to the cluster and perform advanced configuration operations over SSH, or prepare update scripts pushed via deployment tools such as Puppet or Ansible.
% set environments environment base-url https://curity.io
% commit |
For complete automation, the REST API can be used to update any subsystem in Curity. Create new Apps, or update data-backends automatically using REST calls.
The Curity Identity Server is built to scale in both on-premise deployments as well as in cloud deployments. With its unique configuration system, the Curity cluster scales linerarly with no internode dependencies.
Amazon Web Services