2019-12-19 Log In Flow MoM

User team will give us Log In URL that will looks like this:
https://api-shared-stg.test.tvlk.cloud/v2/user/idp/authorize?response_type=code&client_id=d2b93823848c50b70623dd8430b7a688&redirect_uri=http://localhost:51000/callbackToken/en/2cde74a7-1ffc-4480-8377-d03b6bba87d7/callback&scope=openid%20profile%20email%20phone&state=hahahahahah123

In Log In URL parameter, there is redirect_uri. User team will redirect the webpage to redirect_uri after log in is successful. Loka Web FE will provide redirect_url and develop an empty page for redirect_url.

Log In URL needs to be stored somewhere. Storing log in url in front end can cause problem if we need to change it in the future. Instead of storing log in url in front end, log in URL will be stored in Loka Web FE. The plan is:

Android/iOS app open up loka web page (e.g.: manaman.id/login/app)
Loka Web FE will redirect to log in url that provided by user team
If log in is successful, user team will redirect the page to redirect_uri Loka Web FE will display blank page when redirect_uri is opened
Android/iOS app get code parameter from redirect_uri and send it to back end.

OOT from meeting topic: we have problem with deviceId, newer version of android and ios will not have deviceId. This deviceId is needed in tracking and fraud prevention. We still need to figure out how to replace deviceId.