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
Thanks for creating this library, the integration into my project was a breeze but I was surprised that OpenIDConnect.verify/3 is successful when given an expired token.
Shouldn't the documentation explicitly state that verify/3 only checks the token signature and that it's up to the application to validate the token claims?
I understand that, to some degree, claim validation is an application concern but the OpenID spec lists a handful of required ID Token claims, among which are exp and aud. Wouldn't it make sense for an OpenID Connect implementation to validate those standard claims?
The text was updated successfully, but these errors were encountered:
Thanks for creating this library, the integration into my project was a breeze but I was surprised that
OpenIDConnect.verify/3
is successful when given an expired token.Shouldn't the documentation explicitly state that
verify/3
only checks the token signature and that it's up to the application to validate the token claims?I understand that, to some degree, claim validation is an application concern but the OpenID spec lists a handful of required ID Token claims, among which are
exp
andaud
. Wouldn't it make sense for an OpenID Connect implementation to validate those standard claims?The text was updated successfully, but these errors were encountered: