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

[Bela Ban (JIRA)]

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

Bela Ban commented on JGRP-1847:
--------------------------------

Moved to 3.6.4 for posterity...

> 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
>            Reporter: Vojtech Juranek
>            Assignee: Tristan Tarrant
>             Fix For: 3.6.4
>
>
> 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.3.15#6346)