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 current implementation of func (j *JwtVerifier) New() (*JwtVerifier, error) in JwtVerifier sets a fixed timeout of 5 minutes for the cache. It would be beneficial to enhance the function to accept a customizable timeout length during JwtVerifier creation. This modification allows users to tailor the cache mechanism according to their specific use cases, particularly when fetching JWK keys might experience interruptions for durations exceeding the current default timeout, such as 10 minutes.
The text was updated successfully, but these errors were encountered:
I actually ended up rolling my own JWT verification library for similar reasons which you can find here. Using my library you can pass in your own cache when initializing the verifier:
The current implementation of func (j *JwtVerifier) New() (*JwtVerifier, error) in JwtVerifier sets a fixed timeout of 5 minutes for the cache. It would be beneficial to enhance the function to accept a customizable timeout length during JwtVerifier creation. This modification allows users to tailor the cache mechanism according to their specific use cases, particularly when fetching JWK keys might experience interruptions for durations exceeding the current default timeout, such as 10 minutes.
The text was updated successfully, but these errors were encountered: