fix: UI directs to login page when the access token is expired

[Avinashs7]

Description

I have fixed the issue by using the expiry timestamp existing in the user object in localstorage. But I assume it needs to be fixed when it is been rejected in authorization process of each protected route.

Let me know if authorization middleware is done then I can work that as well.

Results

There is an expiry timestamp in the localstorage, change it to nearby time and wait until time crosses and try to request anything in the UI then it will route to login page.
I have tested manually by modifying the expiry time in the localstorage to mimic the real time expiration.
Kindly let me know if any error exists.

Fix #1620

[alfespa17]

Thank you @Avinashs7.

I think it is working correctly, I tested in GITPOD changing DEX configuration and set the token expiration in 2 minutes and the UI is redirected to the login once the token expired.

Example changing the default DEX yaml in /scripts/setup/dex to something like this:

issuer: https://5556-avinashs7-terrakube-plfesnm3bvg.ws-us118.gitpod.io/dex

storage:
  type: memory
web:
  http: 0.0.0.0:5556
  allowedOrigins: ['*']
expiry:
  deviceRequests: "2m"
  signingKeys: "2m"
  idTokens: "2m"
  refreshTokens:
    reuseInterval: "5s"
    validIfNotUsedFor: "5m" 
    absoluteLifetime: "5m" 

[Avinashs7]

@alfespa17 It works, but storing the whole user object as it is done now is not safe. So I believe only the tokens and trivial data should be stored.
It is for security purposes and reduces vulnerabilities. Let me know your thoughts regarding this.

[alfespa17]

@alfespa17 It works, but storing the whole user object as it is done now is not safe. So I believe only the tokens and trivial data should be stored. It is for security purposes and reduces vulnerabilities. Let me know your thoughts regarding this.

If you have any suggestion feel free to create an issue describing the problem and a possible solution

[Avinashs7]

@alfespa17 Sure, Once I will work on it in some time.