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

Bypass 4096-byte limit #354

Open
tschni opened this issue Feb 14, 2025 · 1 comment
Open

Bypass 4096-byte limit #354

tschni opened this issue Feb 14, 2025 · 1 comment

Comments

@tschni
Copy link

tschni commented Feb 14, 2025

I am currently in the process of connecting my company's own internal OAuth IDP via nuxt-auth-utils. I need the access & refresh token in my session.

I need the access token to send it with my API requests in the authorization header (this happens on the server and client side). I need the refresh token to request a new access token if it has expired (this happens on the server side, although I don't yet know exactly how best to implement this :/).

With the two tokens I clearly exceed the 4096-byte limit. What is the best way to store these tokens? I would not like to set up an extra PostgreSQL database for this small use case. Does anyone have any helpful ideas for me?

If anyone has any ideas on how best to implement the refresh token flow, I would also be very grateful. :)

Translated with DeepL.com (free version)

@inthegreenwild
Copy link

+1 this limit has stopped me from using this lib because the JWT I receive is very large and I don't have the ability to shrink it down. Any chance that chunking will be implemented?

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