Progressive Registration

Progressive Registration is used to incrementally collect user data over time. Progressive registration helps to provide a smoother registration experience for customers while also optimizing the customer data available.

On behalf of creating lengthy registration forms with many required fields, you can use progressive registration to get information from your user as time permits, and you can collect user information incrementally in many ways such as second login, or when you reach a particular page or when a particular event triggered. Information is gathered confidentially when it is needed.

cidaas allows you to choose the required fields for the registration page of your application. Different applications can have different registration fields. When an already registered user of Application A tries to login with Application B, then cidaas will ask for data of the registration fields required by Application B to the user.

Implementing Progressive Registration Scenearios

cidaas implemented progressive registration scenarios in the following ways:

1. Application A needs only a few information to register (i.e. Email, Password, Confirm Password).

2. Application B needs more information to register (i.e. Email, User name, Password, Confirm Password, and Date of birth).

3. Now user “X” is registered in Application A and logged into the same.

4. If a user “X” tries to login with Application B, cidaas should ask only the extra fields required by Application B, since basic info of user is already registered in Application A.

Example Illustration

Example illustration of Progressive Registration in cidaas system:

Create Application A and Application B in cidaas admin portal.

1. Consider, your Application A needs only email, password, and confirm password fields to get register.

2. And your Application B needs email, password, confirm password, first name, and last name fields to get register.

We can configure those fields in the advanced settings section of your cidaas application.

1. Navigate to cidaas Admin dashboard -> App Settings -> Edit Application A -> Advance Settings -> Registration Fields. Choose feilds for the registration page of Application A. (i.e, Email, Password, Confirm Password)

2. Navigate to cidaas Admin dashboard -> App Settings -> Application B -> Advance Settings -> Registration Fields. Choose feilds for the registration page of Application B. (i.e, Email, Password, Confirm password, Username, Family name).

3. Register a user "X" in Application A.

After successful registration, the user "X" can use any of the applications in cidaas to login.

4. Now if you try to login to Application B with the credentials of a user registered with Application A.

Then a screen to enter username and family name will be shown since these fields are needed for Application B to register a user.

5. After entering all details click on the Register button to get registered and proceed to login.

Integrate via API

In this section, we are explaining the process of progressive registration via API calls.

1. To continue the login process with Progressive registration, we need to verify the response of the login API mentioned below.

Login API:
{{baseurl}}/login-srv/login or  {{base_url}}/login-srv/login/sdk
API Method  : POST
Request Body :
    "username":"username from login form",
    "password":"password from login form",
    "requestID" : ****************************

If the API returns "417" with the error message "MissingRequiredFields", then you need to go for Missing fields API.

2. Now, call the Missing fields API to proceed with progressive registration to get all the mandatory fields.

Missing  fields API :
path param : track_id

3. Now, you will know the missing fields. Render and update those registration fields in the UI. After entering the fields, to save the registration fields, the user needs to call the Progressive Registration API.

Progressive Registration API:
curl --location -g --request POST '{baseurl}/login-srv/progressive/update/user' 
--header 'requestID: ' 
--header 'trackID: ' 
--header 'Content-Type: application/json' 
--data-raw '{
"customFields": {
"privacy": {
"dataType": "****",
"internal": false,
"key": "privacy",
"lastUpdateFrom": "SELF",
"readOnly": false,
"value": "**********************"
"given_name": "**********************",
"family_name": "**********************"

4. If the consent is missing, the user needs to accept the consent. Call the below-mentioned API.

Consent Management API: 
 API Method: POST

5. After each update of registration fields or consent accepts, the user need to call the following API:

curl '{{baseurl}}/login-srv/precheck/continue/{{track_id}}' --data 'trackId=aab8b099-ce12-4ecf-bf27-39eeb5c63fbd' --compressed

results matching ""

    No results matching ""