[
https://issues.apache.org/jira/browse/ZOOKEEPER-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115136#comment-13115136
]
Mahadev konar commented on ZOOKEEPER-1195:
------------------------------------------
Eugene,
Should we just incorporate ZOOKEEPER-1201 into 3.4? What do you think?
> 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
> Affects Versions: 3.4.0
> Reporter: Eugene Koontz
> Assignee: Eugene Koontz
> Fix For: 3.4.0
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
