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

ASF subversion and git services commented on GEODE-9959:
--------------------------------------------------------

Commit 8659e22805479bb6d3927cdf903dfcb71b4fa2b2 in geode-native's branch 
refs/heads/develop from Mario Salazar de Torres
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=8659e22 ]

GEODE-9959: Add FQDN in log upon SSL missconfig (#904)

- Whenever there is an SSL missoconfiguration while trying to reach a
   locator, an AuthenticationRequiredException is thrown and a log is
   written. Currently FQDN of the locator is not logged.
 - This commit adds the locator FQDN in order to further troubleshoot
   this kind of scenarios.
 - Also, in order to ease implementation, toString method was
   implemented for ServerLocation.

> Add FQDN during SSL handshake error while reaching a locator
> ------------------------------------------------------------
>
>                 Key: GEODE-9959
>                 URL: https://issues.apache.org/jira/browse/GEODE-9959
>             Project: Geode
>          Issue Type: Improvement
>          Components: native client
>            Reporter: Mario Salazar de Torres
>            Assignee: Mario Salazar de Torres
>            Priority: Major
>              Labels: pull-request-available
>
> *WHEN* a geode-native client tries to reach a locator
> *AND* the locator being reached has SSL configured
> *BUT* the geode-native client does not have SSL configured
> *THEN* a log will be written indicating the issue
> *AND* an AuthenticationRequiredException exception will be thrown, which 
> can't be catched
> The improvement proposed here is to log the FQDN of the locator being reached 
> in order to have further information when troubleshooting this kind of issues.



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

Reply via email to