Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to discern user is not authenticated but has returned from oidc callback return address and is still processing? #139

Open
ux-engineer opened this issue Oct 12, 2020 · 1 comment

Comments

@ux-engineer
Copy link

I'd like to display "Routing to authentication service..." message to the user, and once returned back to oidcCallback address from the authentication server, I'd like to display a different message like "Processing authentication...".

How to discern that the user is not authenticated and has not gone to the authentication server yet?

For now it seems I may need to discern this "processing authentication" state by looking at the route path, if it matches to oidc callback route (this could perhaps also be exposed as an getter?) and has some specific route params (like access_token), that the authentication server is supplying...

Could there be a store module state for exposing this state of processing?

@ux-engineer
Copy link
Author

Basically I had to do this kind of logic: !oidcAccessToken && !(window.location.pathname === '/oidc-callback') ? 'Routing to authentication service...' : !oidcAuthenticationIsChecked ? 'Processing authentication...' : 'Fetching data...' where the message is hidden after account's data has been fetched.

So could we add some boolean getter to discern whether authentication process is bootstrapping or is still processing after redirection back from the authentication server, but authentication has not yet been marked as checked?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant