[AMBARI-13853] UI should not use ldap_user field after introducing user_type one.

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.3.0
• Fix Version/s: 2.3.0
• Component/s: ambari-web
• Assignee: Antonenko Alexander
• Reporter: Antonenko Alexander
• Created: 12/Nov/15 10:24
• Updated: 12/Nov/15 17:17
• Resolved: 12/Nov/15 13:27

Description

{
  "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" : [ ]
    }
  ]
}

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.