[
https://issues.apache.org/jira/browse/GEODE-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16288175#comment-16288175
]
ASF subversion and git services commented on GEODE-4076:
--------------------------------------------------------
Commit eb4e948974f35583f0da7d2ca4d2e129b37ef97a in geode's branch
refs/heads/develop from [~jinmeiliao]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=eb4e948 ]
GEODE-4076: throw AuthenticationRequiredException instead of
GemfireSecurityException (#1147)
* GEODE-4076: throw AuthenticationRequiredException when failed to find the
subject of a uniqueId
* added more logging in Client's subject binding/removing
* added more tests for multi clients and multi-user-authentication mode.
> Client receives a GemFireSecurityException instead of
> AuthenticationRequiredException
> -------------------------------------------------------------------------------------
>
> Key: GEODE-4076
> URL: https://issues.apache.org/jira/browse/GEODE-4076
> Project: Geode
> Issue Type: Bug
> Components: security
> Reporter: Jinmei Liao
> Assignee: Jinmei Liao
> Fix For: 1.4.0
>
>
> In some cases, when a client message comes in, the ServerConnection that
> handles this client message fails to find the authenticated user for this
> clientID, the older security framework throws an
> AuthenticationRequiredException while the new Security framework throws
> GemfireSecurityException. This might causes the client not do a retry
> connection.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
