Integration Process Overview

● Kick-off Call: Overview of the whole process & requirements gathering

● SSO UI/UX Flow: A mockup / wireframe of the SSO flow on the Third Party product
should be created.
● Client Registration: To grant the third parties’ access to the Gojek system for certain kinds
of permissions.
● Integration Milestones:
○ Milestone 1: Credential registration & Authorize end point
○ Milestone 2: Token endpoint integration
● Exchange authorization code for tokens [ID token] ❏ Milestone 3: End-to-end testing
● Live to production!

1. Make sure the login of event data with gojek has the following parameters :
● Session data
○ Event_date (Timestamp)
○ Hashed_customer_id (String)
○ Session_id (INT)
● Session time
○ Start_time (Timestamp)
○ End_time (Timestamp)
○ session_length _second (INT)
○ Session_length_each_event_seconds (INT)
○ Avg_time_between_event_second (FLOAT)
● Event in each session
○ First_event (String)
○ Last_event (String)
○ Event_cnt_all (INT)
○ Event_cnt_unique (INT)
○ Top_event (String)
○ Top_event_cnt (INT)

2. The logic to be used for login as follows :

Case 1
Credential Gojek ; Email = A | Phone = 1
Credential Tiket ; Email = A | Phone = 1
Result on Tiket PWA system ; Auto login as Email = A | Phone = 1
If email_verified=’Y’ in gojek then system will auto verified the email address in tiket
If the email status has been verified in tiket then follow existing status

Case 2
Credential Gojek ; Email = A | Phone = 2
Credential Tiket ; Email = A | Phone = 1
Result on Tiket PWA system ; Auto login as Email = A | Phone = 1
If email_verified=’Y’ in gojek then system will auto verified the email address in tiket
If the email status has been verified in tiket then follow existing status

Case 3
Credential Gojek ; Email = A | Phone = 2
Credential Tiket ; Email = B | Phone = 1
Result on Tiket PWA system ; Auto register then login as Email = A | Phone = 2
If email_verified=’Y’ in gojek then system will auto verified the email address in tiket
Send notification to complete the process register by creating a password via the Email
& SMS channel.
Note : Users who have already registered a ticket account via Gojek, can no longer do
register at Tiket.com because their email have already registered at Tiket.com.
If the user tries to register at Tiket.com, then a note "You have registered an account via
Gojek" will be attached, then the user will be directed to set a password

In this case, if the user clicks on the profile page, a pop up will appear to set a password,
if clicked it will send an email to set the password as is.
If the user hasn't verified the password, then this pop will be displayed per session (1
time only per session). If the password has been created then the system will not display
this pop up.

Case 4
Credential Gojek ; Email = A | Phone = 2
Credential Tiket ; Email = B | Phone = 2
Result on Tiket PWA system ; challenge OTP; Auto login as Email = B | Phone = 2;