[KNOX-1210] SSOCookieProvider should detect expired SSO token

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.14.0
• Component/s: KnoxSSO
• Assignee: Sandeep More
• Reporter: Jeff Storck
• Created: 15/Mar/18 21:53
• Updated: 28/Mar/19 14:19
• Resolved: 20/Mar/18 20:25

Description

While proxying a UI that makes XHR (XMLHttpRequest) calls through Knox, if the SSO token expires, that request through Knox will be redirected to the KnoxSSO login page, which will be the response to the request itself.  The UI that receives this response will attempt to parse it and fail, since it is not the expected response; it is the KnoxSSO login page itself.

When a request is made with a 

X-Requested-With

header set to

XMLHttpRequest

the SSOCookieProvider should check for SSO token expiry.  If the token has not expired, the request should continue through to the proxied resource.  If the token has expired, rather than redirecting to the KnoxSSO login page, a

401 Unauthorized

response should be returned.

Issue Links

• blocks: NIFI-4986 Knox SSO token expiry handling (NiFi + Knox + SSO)