This is an automated email from the ASF dual-hosted git repository. dbarnes pushed a commit to branch support/1.15 in repository https://gitbox.apache.org/repos/asf/geode.git
commit c4ed0fcc7ebfa95cf1fdd5816eac40723ef32784 Author: Dave Barnes <[email protected]> AuthorDate: Wed Jun 15 16:26:12 2022 -0700 Incorporated reviewer suggestions --- .../managing/security/implementing_authentication_expiry.html.md.erb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/geode-docs/managing/security/implementing_authentication_expiry.html.md.erb b/geode-docs/managing/security/implementing_authentication_expiry.html.md.erb index 200ce3e87e..b535f1afac 100644 --- a/geode-docs/managing/security/implementing_authentication_expiry.html.md.erb +++ b/geode-docs/managing/security/implementing_authentication_expiry.html.md.erb @@ -23,7 +23,7 @@ Authentication expiry makes it possible for cluster administrators to limit the and peer connections within the cluster. The use of expirable credentials is most common when used in combination with token based authentication and authorization. -Client connections are notified of expiry through the throwing of an `AuthenticationExpiredException` +Client connections are notified of expiry through `AuthenticationExpiredException`, which is thrown in the implementations of `SecurityManager.authenticate` or `SecurityManager.authorize`. Clients will do one automatic attempt to reconnect. Upon receiving a second `AuthenticationExpiredException`
