[
https://issues.apache.org/jira/browse/GEODE-9456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17406921#comment-17406921
]
ASF subversion and git services commented on GEODE-9456:
--------------------------------------------------------
Commit 4af2badab70b0321491b2ddc4e21b8551ea5a368 in geode's branch
refs/heads/develop from Joris Melchior
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4af2bad ]
GEODE-9458: function execution with expiring authentication (#6789)
* GEODE-9456, GEODE-9452: Authentication Expiration (#6721)
* Add tests and throw AuthenticationExpiredException
Co-authored-by: Joris Melchior <joris.melch...@gmail.com>
* GEODE-9460: Add testing for mutli-user scenarios (#6755)
Co-Authored-By Jinmei Liao <jil...@vmware.com>
* review update
* revert accidental change
* GEODE-9458: function execution with expiring authentication
* Changes based on review
* Changes based on review, parameterization
Co-authored-by: Jinmei Liao <jil...@pivotal.io>
> Create AuthenticationExpiredException and have the client handle that
> exception for re-authentication
> -----------------------------------------------------------------------------------------------------
>
> Key: GEODE-9456
> URL: https://issues.apache.org/jira/browse/GEODE-9456
> Project: Geode
> Issue Type: Sub-task
> Components: core, security
> Reporter: Jinmei Liao
> Assignee: Jinmei Liao
> Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.15.0
>
>
> Current: Geode doesn't support any credential expiration
> Desired: Optionally upon every authorization, Geode would check if the
> credential has expired or not, if AuthenticationExpiredException is thrown by
> the SecurityManager, Geode would throw the exception to the client. And the
> client, after receiving the exception, would call "authInitialize" to get a
> new set of credentials and try re-authenticating again. It should only try
> this once.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
