upthewaterspout opened a new pull request, #7598:
URL: https://github.com/apache/geode/pull/7598

   We don't support re-authentication of old clients with server->client queues.
   1.15 and greater clients will receive a new message to trigger
   reauthentication, but older clients have no reliable way to be notified that
   they need to re-authenticate themselves when they have a server->client 
queue.
   
   To make this clear to users, if an AuthenticationExpiredException is ever
   triggered for a client that has a server->client queue and is running a 
version
   less than 1.15, we will return an IllegalStateException to the client. If the
   exception happens while processing the queue we will log a warning and
   immediately disconnect their queue.
   
   <!-- Thank you for submitting a contribution to Apache Geode. -->
   
   <!-- In order to streamline the review of the contribution we ask you
   to ensure the following steps have been taken: 
   -->
   
   ### For all changes:
   - [ ] Is there a JIRA ticket associated with this PR? Is it referenced in 
the commit message?
   
   - [ ] Has your PR been rebased against the latest commit within the target 
branch (typically `develop`)?
   
   - [ ] Is your initial contribution a single, squashed commit?
   
   - [ ] Does `gradlew build` run cleanly?
   
   - [ ] Have you written or updated unit tests to verify your changes?
   
   - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   
   <!-- Note:
   Please ensure that once the PR is submitted, check Concourse for build 
issues and
   submit an update to your PR as soon as possible. If you need help, please 
send an
   email to [email protected].
   -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to