You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2017/09/06 12:38:00 UTC

[jira] [Comment Edited] (ARTEMIS-1372) Support kerberos authentication to LDAP for the LdapJAASLoginModule

    [ https://issues.apache.org/jira/browse/ARTEMIS-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152638#comment-16152638 ] 

Gary Tully edited comment on ARTEMIS-1372 at 9/6/17 12:37 PM:
--------------------------------------------------------------

additional config property for the ldapLoginModule to specify the login.config scope to use for the privileged action when the ldap context env parameter java.naming.security.authentication=GSSAPI

saslLoginConfigScope=broker-sasl-gssapi



was (Author: gtully):
additional config property for the ldapLoginModule to specify the login.config scope to use for the privileged action when the ldap context env parameter java.naming.security.authentication=GSSAPI

loginConfigScope=broker-sasl-gssapi


> Support kerberos authentication to LDAP for the LdapJAASLoginModule
> -------------------------------------------------------------------
>
>                 Key: ARTEMIS-1372
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1372
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>            Reporter: Martyn Taylor
>            Assignee: Gary Tully
>             Fix For: 2.4.0
>
>
> Currently the only mechanisms available for the broker to authenticate into an LDAP server for retrieving user and role information via JAAS, is via username and password, or none (open LDAP server).   We should also add support for Kerberos, which is available in LDAP v3.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)