TNC flow

Overview:

Currently, the system enforces the acceptance of T&C * after the user registers (submits all their information), and logs in. This acceptance of T&C has to happen before/ alongside the submission of the users information (on the registration form).


Current Flow

Approach :


A) Self sign-up

  • After user enters required details for registeration. 
  • Once user registers send TNC details like accepted time stamp, TNC version, and user details in create-user API.
    OR
  • Create a user once successfully created that only call TNC accepted API.

B) SSO  

  • After the user verifies OTP.
  • Once user registers send TNC details like accepted time stamp, TNC version, and user details in create-user API.
    OR
  • Create user once successfully created call after that only TNC accepted API.

C) Google

Conclusion.

A) Self sign-up

  • User opens the registration page.
  • Fetch TNC based on /api/data/v1/system/settings/get/tncConfig API.
  • After user enters required details for registeration. 
  • Create new user and then call tnc acceptance API.

B) SSO  

  • After the user verifies OTP.
  • Fetch TNC based on /api/data/v1/system/settings/get/tncConfig API.
  • After user enters required details for registeration. 
  • Create a new user and then call tnc acceptance API.

C) Google


Telemetry

Interact event will be there

{

  "edata": {
"type": "click",
"subtype": "selected/unselected",
"id": "user:tnc:accept",
"pageid": "self-signup/sso-signup",
}
}


Note - As TNC accept API requires user-auth-token Portal will first generate token for the user and than call accept tnc api