feat: log out user if not authorized

[kptdobe]

Fix #563

Session might expire or user can be logged out for some reason but still continue to author. Editor does not detect this case and still allow user to edit for an infinite time (until page reload).

Test: https://kickout--da-live--adobe.aem.live/

• Sign in to a project
• Open a page for authoring
• Open a new tab with the explorer and sign out
• Go back to editor, make edits. Reload will happen after one or 2s and force user to sign-in again. Minimal changes are lost.

[aem-code-sync]

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
In case there are problems, just click a checkbox below to rerun the respective action.

• Re-run PSI checks
• Re-sync branch

Commits

• a26179a ✅ (latest)
• 97ee222 ✅
• fcc4964 ✅
• b13fd4b ✅
• 5e76a44 ✅
• 9a7f4ca ✅
• 25a9479 ✅
• 6194a85 ✅
• 6eef53e ✅

[aem-code-sync]

	Page	Scores	Audits	Google
📱	/
🖥️	/

[kptdobe]

Need to check.. I get multiple reloads of the page before IMS decides to go to the login page. Weird.

[auniverseaway]

I like this idea. I would probably simplify this, though: If we get a 401 / 403 back from collab, just refresh the page.

The person likely needs to refresh the token they're using for collab. If you use DA at least once every two weeks, you can refresh for up to 364 days. There's no reason to forcefully log them out.

The other advantage is that if they are truly unauthorized now, the existing DA machinery will boot them. Any future improvements we make to the unauthorized flow this will get for free.

[chrischrischris]

This forces the user into the ims signin screen, but is a bit confusing as it does it with no warning. I wonder if we should have a dialog alerting the user with the option to signin again or go to da home? @auniverseaway thoughts?

[auniverseaway]

@chrischrischris I still think a simple refresh is the better thing to do. The IMS machinery can punt the user if they are truly in a logged out state.