You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Andrei Tuicu (Jira)" <ji...@apache.org> on 2020/10/23 14:43:00 UTC
[jira] [Updated] (SLING-9855) Invalidate login token when receiving
401
[ https://issues.apache.org/jira/browse/SLING-9855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Tuicu updated SLING-9855:
--------------------------------
Description:
h3. Story
The Sling testing clients should invalidate login token when receiving 401, so that subsequent requests get a fresh token. Retrying requests with a token for which we already got a 401 response are very likely to continue to fail.
h3. Acceptance Criteria
* The login token is invalidated in the client when Sling responds with 401
cc [~andrei.dulvac]
was:
h3. Story
The Sling testing clients should invalidate login token when receiving 401, so that subsequent requests get a fresh token. Retrying requests with a token for which we already got a 401 response are very likely to continue to fail.
h3. Acceptance Criteria
* The login token is invalidated in the client when Sling responds with 401
> Invalidate login token when receiving 401
> -----------------------------------------
>
> Key: SLING-9855
> URL: https://issues.apache.org/jira/browse/SLING-9855
> Project: Sling
> Issue Type: Improvement
> Components: Apache Sling Testing Clients
> Affects Versions: Apache Sling Testing Clients 2.0.6
> Reporter: Andrei Tuicu
> Priority: Major
>
> h3. Story
> The Sling testing clients should invalidate login token when receiving 401, so that subsequent requests get a fresh token. Retrying requests with a token for which we already got a 401 response are very likely to continue to fail.
> h3. Acceptance Criteria
> * The login token is invalidated in the client when Sling responds with 401
> cc [~andrei.dulvac]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)