You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Joris Melchior (Jira)" <ji...@apache.org> on 2022/01/06 15:49:00 UTC
[jira] [Resolved] (GEODE-9900) Make sure all commands are sending back AuthenticationExpiredException as is
[ https://issues.apache.org/jira/browse/GEODE-9900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joris Melchior resolved GEODE-9900.
-----------------------------------
Resolution: Fixed
Updated the StopCQ and CloseCQ commands and added unit and dunit tests to confirm behaviour.
> Make sure all commands are sending back AuthenticationExpiredException as is
> ----------------------------------------------------------------------------
>
> Key: GEODE-9900
> URL: https://issues.apache.org/jira/browse/GEODE-9900
> Project: Geode
> Issue Type: Bug
> Components: client/server, security
> Affects Versions: 1.15.0
> Reporter: Jinmei Liao
> Assignee: Joris Melchior
> Priority: Major
> Labels: GeodeOperationAPI, needsTriage, pull-request-available
> Fix For: 1.15.0
>
>
> As we have discovered in GEODE-9820, some commands (especially CQ commands) are not sending back `AuthenticationExpiredException` to the client with MessageType.EXCEPTION, hence causing the client not wrapping it in the correct form (See `AbstractOp around L300), We need to:
> 1. go over all the commands and find out what commands are NOT handling the `AuthenticationExpiredExcpetion` correctly.
> 2. fix these commands, catch `AuthenticationExpiredException` specifically and do a `writeException` (leave all other exception handling intact)
> 3. write tests to make sure we are sending the exception to the client.
> #1 would help us determine how many commands are in need of this fix and size this story correctly.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)