You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "Jens Deppe (Jira)" <ji...@apache.org> on 2021/12/07 16:41:00 UTC

[jira] [Commented] (GEODE-9563) Examples for Token Refresh/Reauthentication With Redis Clients

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

Jens Deppe commented on GEODE-9563:
-----------------------------------

After some discussion, we've agreed that automatic refreshing is not required/desired. Rather the expectation is that clients will periodically update their credentials automatically and thus never see an `AuthenticationExpiredException`.

> Examples for Token Refresh/Reauthentication With Redis Clients
> --------------------------------------------------------------
>
>                 Key: GEODE-9563
>                 URL: https://issues.apache.org/jira/browse/GEODE-9563
>             Project: Geode
>          Issue Type: New Feature
>          Components: redis
>            Reporter: Wayne
>            Priority: Major
>              Labels: pull-request-available
>
> The Redis Server and clients do not directly support token refresh or reauthentication.  Write example code of how we can accomplish a forced reauthentication using the existing Redis clients.
>  
> _Acceptance Criteria_
> Example code has been written using the Jedis and Lettuce clients that illustrate how to force these clients to reauthenticate.
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)