-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Deal with 4KB cookie limit for JWT #1103
Comments
Seems like this may provide the best experience (session tokens carried to other tabs) without compromising security: @alexmt LMK your thoughts |
Current JWT handling described here: https://github.com/argoproj/argo-cd/blob/master/docs/security.md |
My investigation revealed that any option that works-around cookies would not work for Instead, we'll modify the application to display a clear error on large cookie. |
Update - theres https://github.com/Yaffle/EventSource that will work I think. |
Is there a plan to fix this in any future release? |
Hi, I also encounter the issue because of large claims acquired. |
It's possible for Argo CD's JWT auth token to be larger than 4KB, which is the maximum size of a HTTP cookie. This limitation was hit after configuring Dex's GitHub
loadAllGroups
flag to return the entire list of group claims for a user.This issue is to find alternative means of dealing with the 4KB limit. Some options:
Note we should not use local storage. For reasons, see: https://dev.to/rdegges/please-stop-using-local-storage-1i04
The text was updated successfully, but these errors were encountered: