/
Capturing Sign-in Type and User Role of users in Pipeline

Capturing Sign-in Type and User Role of users in Pipeline

Jun 24, 2019

Overview :

Need to add the fields in telemetry User role and Sign In type for further breakdown of "No of Unique Users Count by district"

Problem Statement:

  • Stamp user role in telemetry

  • Stamp Sign In type in telemetry

Design:

Stamping User Role -

 Approach-1

  • Portal/App will generating the AUDIT event with userrole(TEACHER,STUDENT) in cdata

             Example:- cdata {

                                userrole: TEACHER/STUDENT

                            }

  • New Samza job will be introduced to capture the AUDIT event

    • Will be  the immediate next job to  extractor so that the other  telemetry events associated with userid will not be skipped from stamping user role

    • Will be capturing audit events and retreive the user role from event and store in redis db

Approach-2

  • Portal/App will generating the AUDIT event with userrole(TEACHER,STUDENT) in cdata

             Example:- cdata {

                                userrole: TEACHER/STUDENT

                            }

  • In Current Extractor Job , we can check for  eid with "AUDIT"  &&  cdata contains "userrole"  key  and add the  "userrole" value to redis with actor.id  (if the audit event is not directly kept in raw topic)

Stamping Sign In Type:

  • In the Denormalisation Job, for the user denorm , we will be caputring the SignIn Type from cassandra user related tables  with below conditions

    • If the user has rootorgid associated with state, then "Validated" user

    • If the user has rootorgid but not state associated, then "Self-Signed" User

    • If the above both conditions fail, then "Anonymous" user

  • Once the SiginType is retreived, the same details will be updated in redis cache and stamped in "userdata" field in telemetry both userrole and Signin type