-
Notifications
You must be signed in to change notification settings - Fork 6.1k
Closed
Labels
in: oauth2An issue in OAuth2 modules (oauth2-core, oauth2-client, oauth2-resource-server, oauth2-jose)An issue in OAuth2 modules (oauth2-core, oauth2-client, oauth2-resource-server, oauth2-jose)status: backportedAn issue that has been backported to maintenance branchesAn issue that has been backported to maintenance branchestype: bugA general bugA general bug
Milestone
Description
Summary
I think the JwtTimeStampValidator uses the wrong error type when a token expires:
Line 93 in 339a053
return new OAuth2Error(OAuth2ErrorCodes.INVALID_REQUEST, reason, |
As listed in https://datatracker.ietf.org/doc/html/rfc6750#section-3.1 it should use INVALID_TOKEN error.
Actual Behavior
JwtTimeStampValidator uses INVALID_REQUEST error when a token expires
Expected Behavior
JwtTimeStampValidator should uses INVALID_TOKEN error when a token expires
Version
5.5.2
Sample
Line 93 in 339a053
return new OAuth2Error(OAuth2ErrorCodes.INVALID_REQUEST, reason, |
gbrehmer
Metadata
Metadata
Assignees
Labels
in: oauth2An issue in OAuth2 modules (oauth2-core, oauth2-client, oauth2-resource-server, oauth2-jose)An issue in OAuth2 modules (oauth2-core, oauth2-client, oauth2-resource-server, oauth2-jose)status: backportedAn issue that has been backported to maintenance branchesAn issue that has been backported to maintenance branchestype: bugA general bugA general bug