Skip to content

Application logs out too quickly in Firefox #128

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

Open
MatthiasvB opened this issue Nov 25, 2022 · 1 comment
Open

Application logs out too quickly in Firefox #128

MatthiasvB opened this issue Nov 25, 2022 · 1 comment
Labels
investigation-needed Issues requires further investigation question This is/seems (currently) more a question than an issue with the code.

Comments

@MatthiasvB
Copy link

I have cloned the repository, npm installed the dependencies, and npm started the dev server.

Works.

I opened the app in Firefox v107.0

I then went to the Admin 2 component, which redirects to the login page. I logged in with my Google account.

I get redirected back to the application, and for a brief moment, I can see all those details about my credentials and the information contained in the token. Works.

A short time later, about 5 seconds after logging in, I seem to get logged out and the token info vanishes too quickly for me to make sense of it.

I navigate to Admin 2 again, now it does a more or less silent refresh - no need for any user interaction.

I see info, I get logged out.

I tried to change silentRefreshTimeout and timeoutFactor in auth.config.ts, but it's no use.

In Edge, it works, so I assume this is a Firefox bug. Do you know what causes it? Is it the same issue you describe for Safari? How do I avoid this issue in my own project?

@jeroenheijmans jeroenheijmans added question This is/seems (currently) more a question than an issue with the code. investigation-needed Issues requires further investigation labels Nov 25, 2022
@jeroenheijmans
Copy link
Owner

I don't actually know, but I do also see this behavior. I suspect it has to do with either third party cookies stuff or other stricter origin checks by Firefox. Those are for the benefit of us as browser users, but unfortunate to deal with as devs. If that's the case, then running your IDS on the same origin is one of the possible solutions.

Someone (e.g. you, yourself) would need to dive into this and investigate, let us know that the deal is here, before we can be sure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
investigation-needed Issues requires further investigation question This is/seems (currently) more a question than an issue with the code.
Projects
None yet
Development

No branches or pull requests

2 participants