[
https://issues.apache.org/jira/browse/ZOOKEEPER-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109364#comment-13109364
]
Hadoop QA commented on ZOOKEEPER-1195:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12495333/SaslAuthNamingTest.java
against trunk revision 1172406.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
-1 patch. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/571//console
This message is automatically generated.
> SASL authorizedID being incorrectly set: should use getHostName() rather than
> getServiceName()
> ----------------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-1195
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1195
> Project: ZooKeeper
> Issue Type: Bug
> Reporter: Eugene Koontz
> Assignee: Eugene Koontz
> Attachments: SaslAuthNamingTest.java, ZOOKEEPER-1195.patch
>
>
> Tom Klonikowski writes:
> Hello developers,
> the SaslServerCallbackHandler in trunk changes the principal name
> service/host@REALM to service/service@REALM (i guess unintentionally).
> lines 131-133:
> if (!removeHost() && (kerberosName.getHostName() != null)) {
> userName += "/" + kerberosName.getServiceName();
> }
> Server Log:
> SaslServerCallbackHandler@115] - Successfully authenticated client:
> authenticationID=fetcher/ubook@QUINZOO;
> authorizationID=fetcher/ubook@QUINZOO.
> SaslServerCallbackHandler@137] - Setting authorizedID:
> fetcher/fetcher@QUINZOO
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
