Industry Standards to Future-Proof Your Investment
In today’s fast-paced and competitive digital world, organizations cannot afford to invest time and money in technology that doesn’t integrate easily with other solutions, creates vendor lock-in, makes it challenging to recruit new talent, or is proven not to be reliable. The Curity identity Server is built on established industry standards that are proven and tested, supporting the security of your organization over the long-term.
Industry Certifications
Curity Identity Server has been certified to conform to the OpenID Connect and Mobile Connect standards. In particular, the Curity product has been self-certified to comply with the basic, implicit, hybrid and configuration protocols of OpenID Connect. Support for Mobile Connect v. 1.1 has been certified by GSMA.
A Growing List of Supported Standards
Curity Identity Server enables the use of a wide range of identity-related standards. It supports a growing list of OAuth, OpenID Connect, SCIM and related protocols from standard bodies such as IETF, OpenID Foundation and OASIS. In addition to integration standards, a large number of user authentication standards such as Kerberos, TOTP and SAML, are also supported.
OAuth
OAuth is an open standard, which provides clients secure delegated access to server resources on behalf of a resource owner. It can be complex though and the Curity Identity Server helps you manage these complexities, making it easier to use, customize and deploy.
RFC or Spec | Name | Purpose of Standard |
---|
OpenID Connect
OpenID Connect is an identity layer on top of the OAuth authorization standard protocol. It allows for verification of an end user’s identity based on authentication performed by an authorization server. The Curity Identity Server has been self-certified to comply with all of the OpenID Connect protocols.
RFC or Spec | Name | Purpose of Standard |
---|
SCIM
System for Cross-domain Identity Management (SCIM) is a standardized and powerful way to perform Create, Read, Update and Delete (CRUD) actions to manage users. The Curity Identity Server utilizes SCIM to hide the complexity of communicating with user account stores behind a standardized interface.
RFC or Spec | Name | Purpose of Standard |
---|
Authentication
The Curity Identity Server also facilitates conformance to authentication specifications such as WebAuthn, Time-Based One-Time Password Algorithm (TOTP) and HMAC-Based One-Time Password Algorithm (HOTP).
RFC or Spec | Name | Purpose of Standard |
---|
Configuration
There are also other protocols used in the Curity Identity Server, used for configuration, access control and alarms for example.
RFC or Spec | Name | Purpose of Standard |
---|
See Curity Identity Server in action
In this demo, we give you a comprehensive overview of the Curity Identity Server. What it is and what problems it helps you solve.
Watch Demo