Antonenko Alexander created AMBARI-13853:
--------------------------------------------
Summary: UI should not use ldap_user field after introducing
user_type one.
Key: AMBARI-13853
URL: https://issues.apache.org/jira/browse/AMBARI-13853
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.1.3
Reporter: Antonenko Alexander
Assignee: Antonenko Alexander
Priority: Critical
Fix For: 2.1.3
{noformat}
{
"href" :
"http://104.196.94.167:8080/api/v1/users/?Users/user_name.matches(.*.*)&fields=*&from=0&page_size=10&_=1443104119309",
"itemTotal" : "2",
"items" : [
{
"href" : "http://104.196.94.167:8080/api/v1/users/admin";,
"Users" : {
"active" : true,
"admin" : true,
"groups" : [ ],
"ldap_user" : false,
"user_name" : "admin",
"user_type" : "LOCAL"
},
"widget_layouts" : [ ],
"privileges" : [
{
"href" : "http://104.196.94.167:8080/api/v1/users/admin/privileges/1";,
"PrivilegeInfo" : {
"privilege_id" : 1,
"user_name" : "admin"
}
}
]
},
{
"href" : "http://104.196.94.167:8080/api/v1/users/jwt-user1";,
"Users" : {
"active" : true,
"admin" : false,
"groups" : [ ],
"ldap_user" : false,
"user_name" : "jwt-user1",
"user_type" : "JWT"
},
"widget_layouts" : [ ],
"privileges" : [ ]
}
]
}
{noformat}
We introduce new field "user_type" instead of "ldap_user" flag as we have more
than two user types now. I guess "ldap_user" field will remain on its place at
lest for some time to provide backward compatibility.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
