When HDAP gets an invalid JWT, it responds with HTTP 401 and suggests HTTP Basic. The browser then pops up a modal to get the user to enter a username and password. On the web generally, that's a helpful workaround. But it you as an end user logged in as bjensen@example.com:hifalutin, you don't necessarily know you need to enter dc=com/dc=example/ou=People/uid=bjensen:hifalutin into the modal.
This patch works around the problem by logging the user out if the JWT has expired before issuing the request. It also adds a closable alert message to let the user know they're being logged out.
It further adds a couple more messages for HTTP 403 Unauthorized and HTTP 500+ errors.
When HDAP gets an invalid JWT, it responds with HTTP 401 and suggests HTTP Basic. The browser then pops up a modal to get the user to enter a username and password. On the web generally, that's a helpful workaround. But it you as an end user logged in as
bjensen@example.com:hifalutin
, you don't necessarily know you need to enterdc=com/dc=example/ou=People/uid=bjensen:hifalutin
into the modal.This patch works around the problem by logging the user out if the JWT has expired before issuing the request. It also adds a closable alert message to let the user know they're being logged out.
It further adds a couple more messages for HTTP 403 Unauthorized and HTTP 500+ errors.