risdenk commented on a change in pull request #274: KNOX-2212 - Token
permissiveness
URL: https://github.com/apache/knox/pull/274#discussion_r385224019
##########
File path:
gateway-server/src/main/java/org/apache/knox/gateway/services/token/impl/DefaultTokenStateService.java
##########
@@ -310,4 +325,30 @@ protected boolean needsEviction(final String token)
throws UnknownTokenException
return tokenExpirations.keySet().stream().collect(Collectors.toList());
}
+ /**
+ * A function that returns the JWT token expiration. This is only called when
+ * gateway.knox.token.permissive.failure.enabled property is set to true.
+ *
+ * @param token token to be verified and saved
+ */
+ protected long getJWTTokenExpiration(final String token) {
+ if (!isValidIdentifier(token)) {
+ throw new IllegalArgumentException("Token data cannot be null.");
+ }
+ JWT jwt;
+ try {
+ jwt = new JWTToken(token);
+ } catch (final ParseException e) {
+ log.errorParsingToken(e.toString());
+ throw new IllegalArgumentException(e);
Review comment:
So its subtle. `getJWTTokenExpiration` is called from the following code:
```
try {
validateToken(token);
} catch (final UnknownTokenException e) {
/* if token permissiveness is enabled we check JWT token expiration
when the token state is unknown */
if (permissiveFailureEnabled && StringUtils
.containsIgnoreCase(e.toString(), "Unknown token")) {
return getJWTTokenExpiration(token);
} else {
throw e;
}
}
```
What this means is that originally the `validateToken` call would throw
`UnknownTokenException`. With this change, the `UnknownTokenException` is
caught and `getJWTTokenExpiration` is called. If `getJWTTokenExpiration` fails,
the code throws `IllegalArgumentException`
So it has the same effect of converting `UnknownTokenException` to
`IllegalArgumentException` based on the settings introduced.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
With regards,
Apache Git Services
