[KNOX-2383] Knox token is expired upon immediate token request after creation

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.5.0
• Fix Version/s: 1.5.0
• Component/s: Server
• Labels: TokenAuth token
• Assignee: Sandor Molnar
• Reporter: Sandor Molnar
• Created: 09/Jun/20 08:06
• Updated: 09/Jun/20 20:42
• Resolved: 09/Jun/20 20:42

Description

Steps to reproduce

1. have a topology with JWT federation provider (let's call it tokenbased) and add a valid HDFS UI service in there (the service itself does not really matter, it's just the fastest way in my environment to reproduce the issue). It's important that you make sure knox.token.exp.server-managed is set to true for the JWT federation provider.
2. get a Knox delegation token using the KNOXTOKEN service. It's important that you make sure knox.token.exp.server-managed is set to true for the KNOXTOKEN service.
3. right after the previous call, try to hit the HDFS UI via the previously created tokenbased topology

Current results

The last action fails as the JWT provider receives the following error:

HTTP ERROR 400 Bad request: token has expired 

Expected results

HDFS UI should have been displayed w/o any issue.

Issue Links

• links to: GitHub Pull Request #341