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

Vojtech Juranek (JIRA) issues at jboss.org
Tue Jun 10 09:07:17 EDT 2014


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

Vojtech Juranek commented on JGRP-1847:
---------------------------------------

Update: kerberos authentication is actually happening and at least in case using {{jgroups/server_name}} nodes obtain valid subjects.

> SASL GSSAPI auth doesn't use 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
>
> 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.3#6260)


More information about the jboss-jira mailing list