[
https://issues.apache.org/jira/browse/AMBARI-16205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Toader updated AMBARI-16205:
--------------------------------------
Description: As AMBARI-15554 allows users with the same sAMAccountName (in
the case of AD) but different UPN's to be mapped to the same Ambari user, which
will be the desired behavior for most of the users, however some will not want
that functionality. So we need the ability to turn it off, and have it off by
default. Ambari should let the user know that was not able to log in the user
due to too many matches found which will cue their admin in to enable this
feature. (was: As AMBARI-16119 allows users with the same sAMAccountName (in
the case of AD) but different UPN's to be mapped to the same Ambari user, which
will be the desired behavior for most of the users, however some will not want
that functionality. So we need the ability to turn it off, and have it off by
default. Ambari should let the user know that was not able to log in the user
due to too many matches found which will cue their admin in to enable this
feature.)
> Disable alternate user search functionality by default
> ------------------------------------------------------
>
> Key: AMBARI-16205
> URL: https://issues.apache.org/jira/browse/AMBARI-16205
> Project: Ambari
> Issue Type: Task
> Reporter: Sebastian Toader
> Assignee: Sebastian Toader
> Priority: Critical
>
> As AMBARI-15554 allows users with the same sAMAccountName (in the case of AD)
> but different UPN's to be mapped to the same Ambari user, which will be the
> desired behavior for most of the users, however some will not want that
> functionality. So we need the ability to turn it off, and have it off by
> default. Ambari should let the user know that was not able to log in the user
> due to too many matches found which will cue their admin in to enable this
> feature.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)