[
https://issues.apache.org/jira/browse/NIFI-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15671698#comment-15671698
]
ASF GitHub Bot commented on NIFI-3020:
--------------------------------------
GitHub user mcgilman opened a pull request:
https://github.com/apache/nifi/pull/1236
LDAP - Configurable strategy to identify users
NIFI-3020:
- Introducing a user identity strategy for identifying users.
- Fixing issue with the referral strategy error message.
- Adding code to shutdown the application when the authorizer or login
identity provider are not initialized successfully.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mcgilman/nifi NIFI-3020
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/1236.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 #1236
----
commit 252e3bae209bb7d4365dd28dded7e72048e38e41
Author: Matt Gilman <[email protected]>
Date: 2016-11-16T21:29:14Z
NIFI-3020:
- Introducing a strategy for identifying users.
- Fixing issue with the referral strategy error message.
- Adding code to shutdown the application when the authorizer or login
identity provider are not initialized successfully.
----
> LDAP - Support configurable user identity
> -----------------------------------------
>
> Key: NIFI-3020
> URL: https://issues.apache.org/jira/browse/NIFI-3020
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Matt Gilman
>
> The current LDAP provider supports a configurable search filter that will
> allow the user specified login name to be matched against any LDAP entry
> attribute. We should offer a configuration option that will indicate if we
> should use the LDAP entry DN or if we should use the login name that was used
> in the search filter. For instance, this would allow an admin to configure a
> user to login with their sAMAccountName and subsequently use that name as
> their user's identity.
> Note: we should default this option to be the user DN in order to ensure
> backwards compatibility.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
