SASL GSSAPI auth doesn't use principal configured login_module

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.