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

NEXT THIS: Migrate to session based auth #12

Open
PhilippMDoerner opened this issue Nov 14, 2024 · 1 comment
Open

NEXT THIS: Migrate to session based auth #12

PhilippMDoerner opened this issue Nov 14, 2024 · 1 comment

Comments

@PhilippMDoerner
Copy link
Owner

Server sets up the session-id/token in a HTTP-only cookie and puts it on strict-mode so that only your domain has access to it.

@PhilippMDoerner PhilippMDoerner changed the title Migrate to session based auth NEXT THIS: Migrate to session based auth Nov 17, 2024
@PhilippMDoerner
Copy link
Owner Author

We re having serious refresh issues.
The problems:

  • Often a second request fires a refresh while another request is already refreshing (Note: DO NOT Mix this up with "Request A and B fire simultaneously and thus both may trigger a refresh
  • Often you fire all refreshes immediately and the token in localstorage is not consistent with the latest data
  • Generally the order in which the tokenInterceptor does things is driving me crazy

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