You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/01/10 16:36:00 UTC
[jira] [Commented] (ARTEMIS-1597) Krb5LoginModule will succeed on
null principal in error
[ https://issues.apache.org/jira/browse/ARTEMIS-1597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16320561#comment-16320561 ]
ASF GitHub Bot commented on ARTEMIS-1597:
-----------------------------------------
GitHub user gtully opened a pull request:
https://github.com/apache/activemq-artemis/pull/1767
[ARTEMIS-1597] validate non null callback principal for login success
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gtully/activemq-artemis ARTEMIS-1597
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/1767.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1767
----
commit 23a4d583d7ebd350930da1f8fa8f0074f6de1d5a
Author: gtully <ga...@...>
Date: 2018-01-10T16:33:33Z
[ARTEMIS-1597] validate non null callback principal for login success
----
> Krb5LoginModule will succeed on null principal in error
> -------------------------------------------------------
>
> Key: ARTEMIS-1597
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1597
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 2.4.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 2.5.0
>
>
> The Krb5LoginModule which is used to optionally map a krb5 authenticated principal for role mapping will add a null principal in error. This null user is harmless but it will get in the way of login module chaining that depends on failure to propagate down the list.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)