-
Notifications
You must be signed in to change notification settings - Fork 300
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
Cookie token too big when using IDP #1838
Comments
We can alternatively chunk the cookie, like we did for the hop usecase @Alevsk |
Cookie Chunks 🍪🍪🍪🍪 |
is this finished @dvaldivia ? |
Hi everyone |
This is not a priority for us at the moment. If you have too many roles/claims in your IDP the token may become too big, feel free to open a PR to fix it. |
When using IDP, the provider may return a big JWT token.
This JWT is part of the SessionToken and may be used later.
Apparently, in Minio Console, all the credentials are marshalled and then encrypted and finally turned into a base64:
console/pkg/auth/token.go
Lines 127 to 137 in 5e10719
This may end up with a Cookie bigger than 4096 bytes, and then not being persisted by the browser and used later.
A possible solution (if accepted) would be to use some compression before encryption, in a way that the raw text/string can be reduced, and then encrypted (in a cost of probably a bit more CPU).
The opposite should happen as well. So one suggestion:
Testing locally, and using default gzip compression, a 4500 bytes cookie could be properly reduced to 2589 bytes, and then the authentication moving forward without any problem.
If this is accepted by the community, I can raise a PR changing encrypt/decrypt Claims to compress before encrypt.
The text was updated successfully, but these errors were encountered: