You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue is that when I create a custom encoder that takes the token generated by encoder.lcobucci and re-encrypts it, the cookies don't work, but the headers do. From what I've been able to verify, is because the cookies call a JWTSplitter class, and since the new token is encrypted, it doesn't have the JWT format (header.payload.signature). What's curious is that the headers don't call this class, so the custom encoder can encode and decode without any problems.
Is there any way to create any cookie provider?
Can JWTCookieProvider class use the encoders before calling JWTSplitter?
The issue is that when I create a custom encoder that takes the token generated by
encoder.lcobucci
and re-encrypts it, the cookies don't work, but the headers do. From what I've been able to verify, is because the cookies call aJWTSplitter
class, and since the new token is encrypted, it doesn't have the JWT format (header.payload.signature). What's curious is that the headers don't call this class, so the custom encoder canencode
anddecode
without any problems.Is there any way to create any cookie provider?
Can
JWTCookieProvider
class use the encoders before callingJWTSplitter
?I'm using the following configuration:
Custom encoder
The text was updated successfully, but these errors were encountered: