[
https://issues.apache.org/jira/browse/GEODE-9663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17425022#comment-17425022
]
ASF subversion and git services commented on GEODE-9663:
--------------------------------------------------------
Commit ccccc5e8031f314c3d58df0ba7bbdf0d68704bdb in geode's branch
refs/heads/GEODE-9567-next-geode-for-redis-rename from Jinmei Liao
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ccccc5e ]
GEODE-9663: throw and handle AuthenticationExpiredException at login time
(#6927)
* GEODE-9663: throw and handle AuthenticationExpiredException at login time
> 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
>
> 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)
