[
https://issues.apache.org/jira/browse/NIFI-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Gilman updated NIFI-3020:
------------------------------
Description:
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 capability.
was:
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. 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 capability.
> 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 capability.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
