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

Problem with cookie size because of refresh_token #40

Open
dmaragkos opened this issue Jan 3, 2025 · 1 comment
Open

Problem with cookie size because of refresh_token #40

dmaragkos opened this issue Jan 3, 2025 · 1 comment

Comments

@dmaragkos
Copy link

Hi,

I am having an issue because the OKDP_AUTH_SPARK_UI cookie size is exceeding the 4KB limit. The issue is caused by the refresh_token which is too long. Is there a way to overcome the issue, e.g. configuration parameter to ignore refresh_token?

Thank you in advance

@idirze
Copy link
Contributor

idirze commented Jan 20, 2025

Hello,
Thank you for the issue and we apologize for the delay.

Have you tried omitting offline_access from the scope or AUTH_SCOPE depending on your configuration?

Instead of providing the scope openid+profile+email+roles+offline_access, you can provide openid+profile+email+roles for example by omitting offline_access and check if your OAuth2 or OIDC provider returns the refresh token.

Note

We store the token information in a cookie (encrypted + compressed) as spark history (or ui) does not support natively http session management and conceptually we wanted to keep the plugin as simpler as possible without extra reverse proxy for session management.

Let us know so that we can provide a patch.

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

2 participants