Like most digital identity platforms, Gluu persists user data. How can you manage this data?

SCIM, or the System for Cross-domain Identity Management specification, is an open standard API which defines RESTful endpoints, a schema and a protocol to manage user identity information. For example, you can POST to the SCIM /Users endpoint to add a user, or perform a GET to that endpoint to search users.  The SCIM component of Gluu is a server implementation of SCIM. By calling this API, you can add, delete and edit user information in the Gluu platform. For example, if you are implementing a registration website, you would call the SCIM endpoint to add the user to your Gluu Server.

The SCIM API should never be accessed anonymously. However, the standard itself doesn’t define a mechanism to prevent unauthorized requests to endpoints. There are just a few guidelines for authentication and authorization in section 2 of RFC 7644.

In the Gluu Server, the default protection mechanism for SCIM APIs is UMA, a profile of OAuth 2.0. This means you’re software will need to obtain an UMA access token before you call the SCIM API. Gluu also provides a “Test Mode” static token, which like its name suggests, can be used for testing (but don’t use static tokens for production!)

An open source, enterprise IAM platform you can depend upon long-term.

« »