[KNOX-2377] Address potential loss of token state

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5.0
• Component/s: Server
• Assignee: Philip Zampino
• Reporter: Philip Zampino
• Created: 04/Jun/20 20:00
• Updated: 16/Jun/20 13:34
• Resolved: 16/Jun/20 13:34

Description

With the recent performance enhancements associated with token state management (KNOX-2375), there has come the possibility of token state getting lost.

Part of the performance improvement is removing the persistence of token state to the keystore (which is expensive) from the token request processing path, and performing that persistence in a background thread.

It's possible that the gateway could crash or otherwise go down before the state of recently-issued tokens has been persisted to the keystore. Consequently, after the gateway is restarted, subsequent use of these "lost" tokens would result in client authentication failures because the tokens would be unknown to the TokenStateService.

The TokenStateService needs to be able to recover from such scenarios to avoid the loss of token state.

Issue Links

• links to: GitHub Pull Request #345