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

Multiple browser tabs send different refresh_token request with OpenID Connect at same interval #10959

Open
inferno-umar opened this issue May 24, 2024 · 2 comments
Labels
Priority:p3-medium Normal priority Type:Bug Something isn't working

Comments

@inferno-umar
Copy link

Steps to reproduce

  1. Use oCIS with openid connect with less refresh_token interval
  2. Open multiple oCIS tabs considering they share same browser's LocalStorage
  3. Inspect the requests in all these tabs for refresh_token

It is observed that a token response in 1 tab requests for refresh_token in another tab before the access_token expires at the same interval.

There must be token inspection & mutex used I guess while refresh_token request is sent!

@inferno-umar inferno-umar added the Type:Bug Something isn't working label May 24, 2024
@rhafer
Copy link

rhafer commented May 24, 2024

Transferring to web ...

@rhafer rhafer transferred this issue from owncloud/ocis May 24, 2024
@kulmann kulmann added the Priority:p2-high Escalation, on top of current planning, release blocker label May 29, 2024
@kulmann kulmann added Priority:p3-medium Normal priority and removed Priority:p2-high Escalation, on top of current planning, release blocker labels May 29, 2024
@kulmann kulmann moved this from Qualification to Prio 3 or less in Infinite Scale Team Board May 29, 2024
@JammingBen
Copy link
Contributor

Seems to be an issue in the oidc-client-ts lib, see authts/oidc-client-ts#430.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority:p3-medium Normal priority Type:Bug Something isn't working
Projects
Status: Prio 3 or less
Development

No branches or pull requests

4 participants