DevOps, CI/CD and Automation

Hi Yogesh,

Take a look at the Cookbook example for the router at https://www.oracle.com/webfolder/technetwork/jet/jetCookbook.html?component=corerouter&demo=module
Setting up the new router should be fairly similar to the old one.
I implemented the login screen in my application as follows. (Don't know if this is best practise, but it works.) This is also very similar to the router example above.
Create a oj-module element in your main/index HTML to switch between login and content screens/modules.
During application startup - e.g. in your root viewmodel constructor - configure the router paths for login and content. Default should be login.
Check the login status of the user. If login is valid, directly navigate to content; Else stay on the login page.
(Optional) If you have more than one content-screen/module you may want to return your user to the one he last visited (if the login is still valid). In this case, I made a simple extension to the OJ CoreRouter which keeps track of the last routing state in the SessionStorage. I then simply restore the cached state.

Obviously, you will need to change this for the GoogleAPI, e.g. the validateToken() call would need to be replaced/changed.

Kind Regards,
Philip