You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Jinmei Liao (Jira)" <ji...@apache.org> on 2021/10/06 18:00:00 UTC

[jira] [Resolved] (GEODE-9663) throw and handle AuthenticationExpiredException at login time

     [ https://issues.apache.org/jira/browse/GEODE-9663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jinmei Liao resolved GEODE-9663.
--------------------------------
    Fix Version/s: 1.15.0
       Resolution: Fixed

> throw and handle AuthenticationExpiredException at login time
> -------------------------------------------------------------
>
>                 Key: GEODE-9663
>                 URL: https://issues.apache.org/jira/browse/GEODE-9663
>             Project: Geode
>          Issue Type: Sub-task
>            Reporter: Jinmei Liao
>            Assignee: Jinmei Liao
>            Priority: Major
>              Labels: GeodeOperationAPI, pull-request-available
>             Fix For: 1.15.0
>
>
> There is a time gap between credentials are gathered at the client and credentials are examined on the server, if between this time period, credentials expired (rare case, but it does happen a lot during stress tests, see `AuthExpirationMultiServerDunitTest.consecutivePut` test), client operations might fail during the operations (even after user is authenticated, doing a put/get might need to open new connections and require authentication again). So we should allow "authenticate" method also throw AuthExpirationException if they want to give client a chance to retry (only retry once).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)