[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flavio Junqueira updated ZOOKEEPER-2606:
----------------------------------------
    Fix Version/s: 3.6.0
                   3.5.3
                   3.4.10

> SaslServerCallbackHandler#handleAuthorizeCallback() should log the exception
> ----------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-2606
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2606
>             Project: ZooKeeper
>          Issue Type: Bug
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>            Priority: Minor
>              Labels: security
>             Fix For: 3.4.10, 3.5.3, 3.6.0
>
>         Attachments: ZOOKEEPER-2606.v1.patch
>
>
> {code}
>             LOG.info("Setting authorizedID: " + userNameBuilder);
>             ac.setAuthorizedID(userNameBuilder.toString());
>         } catch (IOException e) {
>             LOG.error("Failed to set name based on Kerberos authentication 
> rules.");
>         }
> {code}
> On one cluster, we saw the following:
> {code}
> 2016-10-04 02:18:16,484 - ERROR 
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:SaslServerCallbackHandler@137] - 
> Failed to set name based on Kerberos authentication rules.
> {code}
> It would be helpful if the log contains information about the IOException.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to