[M] Warn admin user if session has timed out in DUP admin

[manuji]

As a DUP admin user (park operator, bc parks staff), I want to be warned if my session within DUP admin has timed out so that I know what happened and can log in and re-try.

Acceptance Criteria:

• if user's session in keycloak has timed out while they are on a page, an error message is provided after the next action they take to let them know they need to log in again.

Dev Checklist:

• [ ] Keycloak service handling improvements
• [ ] implement stubbed out functions in keycloakservice.ts

Note:

• this will likely be something we need to do across A&R, DUP, and DR
• there are a number of functions in keycloakservice.ts that are called based on a variety of events that are triggered by the KC realm. Such as, tokenRefreshSuccess/Fail, etc.. Find these empty functions, and implement the correct response. Sometimes it will be to redirect to the /login page, other times, show an error.. it will depend on the function in question.

Original Bug: Parent ticket: https://github.com/bcgov/parks-reso-admin/issues/325

Scenario:

• Navigate to the DUP-Admin on TEST: https://d3jkh5unv9de6y.cloudfront.net/dayuse/
• Log in as a sysAdmin
• Navigate to the FAQ page and then add content
• Try to save the content after like 15 minutes/after the page has timed-out.

Issue:

• When the content is saved after the page has timed out, the confirmation message is displayed but after that neither success nor error message is displayed.

[Christopher-walsh22]

@manuji After the page times out and you confirm you want to make the changes; Why happens to the information you are saving? Does it successfully save or does it fail? I am currently try to reproduce

[manuji]

Hi @Christopher-walsh22 , no, the data wasn't saved. I lost my changes when I refreshed the page.

[Christopher-walsh22]

@manuji After do some digging into this one I think its related to accessing restricted pages after you've timed out. You would need to be re-authenticated to allow the form to submit. If the form isn't submitting then there wouldn't be an api response to trigger the toast message. I can dig further into this one but it feels like it would be how DUP uses key cloak at a higher level rather than an problem with the FAQ page. We should discuss this further at the next refinement session if needed.

[JLWade]

Moving out of sprint 7 - this is something that should likely be addressed across all of our admin platforms - an error page to make users aware when they have timed out.

[Dianadec]

Notes from Mark during refinement:

Applicable to all products - admin front-ends - the keycloak service in FEs are lacking some of the implementation

• tldr: when a session expires due to the session max being hit, we are not handling it - if we did, we'd be redirecting back to OIDC login (idir, services card, etc).
• Right now it doesn't do anything, it just sits on the page. Sends a stale token.