[
https://issues.apache.org/jira/browse/AMBARI-14187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15038601#comment-15038601
]
Hudson commented on AMBARI-14187:
---------------------------------
ABORTED: Integrated in Ambari-trunk-Commit #3960 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3960/])
AMBARI-14187. Restrict creating JWT user if local one with same name
(mpapyrkovskyy:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4ab6afc2ff187ab5ff597d20dd51d1e46c982080])
*
ambari-server/src/main/java/org/apache/ambari/server/security/authorization/jwt/JwtAuthenticationFilter.java
*
ambari-server/src/main/java/org/apache/ambari/server/security/authorization/Users.java
* ambari-server/src/main/java/org/apache/ambari/server/orm/dao/UserDAO.java
*
ambari-server/src/main/java/org/apache/ambari/server/security/authorization/jwt/JwtAuthentication.java
> Restrict creating JWT user if local one with same name exists
> -------------------------------------------------------------
>
> Key: AMBARI-14187
> URL: https://issues.apache.org/jira/browse/AMBARI-14187
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Myroslav Papirkovskyy
> Assignee: Myroslav Papirkovskyy
> Priority: Critical
> Fix For: 2.4.0
>
>
> Due to current users API limitation, Ambari cannot handle users with same
> name but different types.
> So we should try to avoid such conflicts.
> This is temporary solution until API change.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
