[jira] [Commented] (GEODE-9454) The client, if multiple operations are in flight, should not flood the authentication server with re-authentication requests.

["Jinmei Liao (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GEODE-9454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17437069#comment-17437069 ] 

Jinmei Liao commented on GEODE-9454:
------------------------------------

Since we are reusing the uniqueId for the same serverConnection, clients threads sharing the connection will send in the uniqueId of the re-authenticated subject from previous thread, thus eliminating the need for this thread to re-authenticate. This should be achieved already.

> The client, if multiple operations are in flight, should not flood the authentication server with re-authentication requests.
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-9454
>                 URL: https://issues.apache.org/jira/browse/GEODE-9454
>             Project: Geode
>          Issue Type: Sub-task
>          Components: core, security
>            Reporter: Jinmei Liao
>            Priority: Major
>              Labels: GeodeOperationAPI
>
> the blocking should only be for one client only
> Having a test with multiple clients with multiple thread doing cache operations
> The test should also cover the multi-user authentication mode



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