Repository navigation
currentSession doesn't check if token is still valid on Solid server. #127
Description
Current Functionality: tracksession check if there is a token in the local storage to validate if the user is logging or not.
Possible issue: Apps doesn't know when the token is invalid to redirect the user to log in. We could use 401 response to fix it but we couldn't make a difference between a token or permissions error.
Solution: New functionality to check if the current session(token) is valid on Solid server and make differences when there is an error for permissions or token.
cc: @RubenVerborgh
Activity
[-]tracksession doesn't check is token is still valid on Solid server.[/-][+]currentSession doesn't check is token is still valid on Solid server.[/+]RubenVerborgh commentedon Jun 20, 2019
Technically
currentSessionofwebid-oidc.js.Main problem is that token renewal is not implemented in the OIDC libraries we use.
[-]currentSession doesn't check is token is still valid on Solid server.[/-][+]currentSession doesn't check if token is still valid on Solid server.[/+]matthieu-fesselier commentedon Jun 12, 2020
Interested in this too!
I'm not sure, but token renewal is here where there is no token on the client and we need to get a new one from the servern right?
What if there is still a token on the client but it's not valid anymore on the server? Can we check that?