Managing users is a headache for many organizations, with multiple data sources to consider and keep up to date. Your users may be stored in some old SQL server, or LDAP repository, or maybe a combination of many.
Curity’s User Management service is OAuth protected and expose a single standardized CRUD API that your applications and services can interact with, removing the pain of disparate user repositories.
Facilitates simplified and standardized user management using one single API that integrates with multiple data sources.
Using the Curity OAuth server, your user management APIs are protected from the start. It can be configured with fine-grained authorization, allowing different users and applications access to different operations and user-data. This facilitates streamlined integration with existing customer support systems and user portals.
User CRUD (Create Read Update Delete) is needed everywhere. The Customer service application needs to update users, other applications may need to read attributes about users, and batch services need to sync users between domains.
With Curity Identity Server user CRUD has never been easier. Using SCIM 2.0 there is a standard REST API for all of these operations making the development process a whole lot easier.
Using the User Management Service, you can view, list and manage the active sessions and devices for a user with a single API. Sessions can be revoked when needed, and you can let the user view its own session or allow an admin to view the user's sessions. This significantly simplifies the development and maintenance of user management applications and services.
Curity’s User Management Service provides support for any database. User credentials can be in Active Directory and other user data in a NoSQL-datastore. Here are just a few examples where the User Management Service has been used and verified:
Google Cloud SQL
Microsoft SQL Server
In this demo, we give you a comprehensive overview of the Curity Identity Server. What it is and what problems it helps you solve. Approximately 30 minutes.Watch Demo