[
https://issues.apache.org/jira/browse/AMBARI-17715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988978#comment-15988978
]
Lars Francke commented on AMBARI-17715:
---------------------------------------
I missed this part from the Reviewboard link:
{quote}
Due to API limitations we cannot login JWT user if LDAP/LOCAL one with same
name already exists.
We should temporary threat JWT users as LDAP ones and rely on ldap-sync process
for user creation, as this is most frequent configuration.
{quote}
So LDAP is now mandatory to use JWT/SSO?
This probably warrants a follow-up JIRA, no?
> Not able to login using KnoxSSO if local/ldap Ambari User with same name
> exists
> -------------------------------------------------------------------------------
>
> Key: AMBARI-17715
> URL: https://issues.apache.org/jira/browse/AMBARI-17715
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Myroslav Papirkovskyi
> Assignee: Myroslav Papirkovskyi
> Priority: Blocker
> Fix For: 2.4.0
>
>
> Due to API limitations we cannot login JWT user if LDAP/LOCAL one with same
> name already exists.
> We should temporary threat JWT users as LDAP ones and rely on ldap-sync
> process for user creation, as this is most frequent configuration.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
