[jboss-jira] [JBoss JIRA] (JGRP-1847) SASL GSSAPI auth doesn't use principal configured login_module

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/JGRP-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986494#comment-12986494 ] 

RH Bugzilla Integration commented on JGRP-1847:
-----------------------------------------------

Misha H. Ali <mhusnain at redhat.com> changed the Status of [bug 1116311|https://bugzilla.redhat.com/show_bug.cgi?id=1116311] from VERIFIED to CLOSED

> SASL GSSAPI auth doesn't use principal configured login_module
> --------------------------------------------------------------
>
>                 Key: JGRP-1847
>                 URL: https://issues.jboss.org/browse/JGRP-1847
>             Project: JGroups
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Vojtech Juranek
>            Assignee: Tristan Tarrant
>
> When referring GSSAPI login module (e.g. kerberos login module in WildFly) in jgroups sasl setup, the login module seems to be ignored. JGroups try to log-in with different principal than one configured in login module (it uses default principal {{jgroups/server_name}}) and also I don't see any attempt to use WildFly login module  in kerberos log.
> Not sure if related, but when I setup principal {{jgroups/server_name}} in Kerberos, authentication also fails and again it I don't observe any attempt to log-in in Kerberos log.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)