Streamline Identity Management with SCIM
Enhance your Identity Management Experience with SCIM. Simplify user provisioning and management across different systems seamlessly.
simplifies and automates the entire process. With Cripsa, your customer can provision or deprovision users and groups directly from their identity providers. Self-serve dashboard help your customer to share with their IT team to configure it.
Seamlessly integrates with your enterprise's existing systems, including corporate directories and HRIS platforms, to enhance user lifecycle management within your application. Through a single integration, users, groups, and access controls can be automatically provisioned and deprovisioned, streamlining the process and eliminating the need for manual updates.
Connect your existing identity systems with Cripsa's SCIM support.
Tailor SCIM implementation to suit your organization's unique requirements.
Simplify user provisioning, updates, and deactivation across platforms.
Keep your identity systems in sync for up-to-date information.
The Cripsa User sync store is a key/value pair store linked to an Cripsa UserPool identity. There is no limit to the number of identities you can create in your identity pools and sync store. Each Cripsa UserPool identity within the sync store has its own user information store.
Data associated with an Cripsa UserPool identity are organized as key/value pairs. A key is a label e.g. “MusicVolume”, and a value e.g. “11”. Key/value pairs are grouped and categorized using data sets. Data sets are a logical partition of key/value pairs and the most granular entity used by Cripsa UserPool to perform sync operations.
Each user information store can have a maximum size of 20MB. Each data set within the user information store can contain up to 1MB of data. Within a data set you can have up to 1024 keys.
Both keys and values within a data set are alphanumeric strings. There is no limit to the length of the strings other than the total amount of values in a dataset cannot exceed 1MB. Binary data can be stored as a base64 encoded string as a value provided it does not exceed the 1MB limit.
No, a user identity and information store are tied to a specific Cripsa Developer account. If there are multiple apps from different publishers on a particular device that use Cripsa UserPool, each app will use the information store created by each publisher.
Limiting the data set size to 1MB increases the chances of a synchronization task completing successfully even when bandwidth is limited without lots of retries that consume battery life and data plans.
Cripsa UserPool Events allows developers to test run with few user data and see the logs. Through the log one can find the issue, if any. Once the template is ready then only the customer prepare final sheet of all the users and use it in Production Landscape for Synchronization of User Data.
You can use Cripsa UI provided in portal and upload the CSV file which contains the user data to synchronize all the use data in your user pool id. Also you can validate the synchronization by seeing the logs through Cripsa UI itself.
By default Cripsa UserPool maintains the last-written version of the data. If the user information already presents in UserPool then it will not overwrite rather you will get an error message in the log for that particular user about already value existing error.
A dataset is a collection of key-value pairs in Cognito Sync that store user-specific data. Datasets are associated with Cognito identities, allowing you to synchronize data across devices for a particular user.