[AMBARI-15479] JwtAuthenticationFilter needs to accommodate null JWT expiration time

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: ambari-server
• Assignee: Larry McCay
• Reporter: Larry McCay
• Created: 18/Mar/16 13:02
• Updated: 19/Apr/16 17:10
• Resolved: 19/Apr/16 17:09

Description

Current validation of the JWT token within the SSO cookie interprets no expiration date as expired and redirects to acquire a new cookie. In the JWT specification exp is an optional claim however. KnoxSSO is leveraging this to mean that the token lifecycle should be tied to that of the SSO cookie itself and not timeout from underneath the cookie.

This minor change will allow null expiration times within the JWT token to be considered valid.

Issue Links

• links to: ReviewBoard
• mentioned in: Page Loading...