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

Remove the encrypted payload from AuthCode and RefreshToken #1470

Open
wants to merge 70 commits into
base: master
Choose a base branch
from

Conversation

craigp1231
Copy link

The Auth Code and Refresh Token information can be stored in the repository and doesn't have to go in the payload. This will reduce auth code and refresh token size, but will require more calls to the repository.

If the user specifies an encryption key, the payload will be attempted to be encrypted or decrypted, else they are returned from the respective repositories.

craigp1231 and others added 30 commits January 19, 2025 23:52
The Auth Code and Refresh Token information can be stored in the repository and doesn't have to go in the payload. This will reduce auth code and refresh token size, but will require more calls to the repository
hafezdivandari and others added 29 commits February 15, 2025 17:00
formatting

formatting

formatting

fix backward compatibility

bump lcobucci/jwt
The Auth Code and Refresh Token information can be stored in the repository and doesn't have to go in the payload. This will reduce auth code and refresh token size, but will require more calls to the repository
@Sephster
Copy link
Member

Hi @craigp1231 - is it possible to bring this in line with master so I can review? I was also wondering if you could outline why you want this change. Historically, we have deliberately set the library up this was to reduce repository access overhead. I'd be keen to understand why the token size is an issue. Thank you

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

Successfully merging this pull request may close these issues.

4 participants