Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.4.0
-
None
-
None
Description
When the KnoxToken service is used to revoke/cancel a token, the current behavior is to persist the revoked status of the token. The problem is that token state is never removed from, in the case of the AliasService-based implementation, the keystore. There is no real requirement to differentiate between a known-but-revoked token and and unknown token; Therefore, the state for a revoked token can be removed altogether.
Attachments
Issue Links
- is related to
-
KNOX-2214 Reaping of expired Knox tokens
- Resolved
- links to