You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Greg Hill (JIRA)" <ji...@apache.org> on 2016/01/14 19:32:39 UTC
[jira] [Updated] (AMBARI-14672) Creating a user with a mixed-case
username behaves strangely
[ https://issues.apache.org/jira/browse/AMBARI-14672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Greg Hill updated AMBARI-14672:
-------------------------------
Description:
If you create a user with some capital letters in the username, Ambari accepts the request and creates a user with the lowercase version of that username. However, if you then do a GET on the original username, Ambari gives a 200 response but an empty response body:
{noformat}
GET /api/v1/users/MixedCase
200 OK
<empty response>
GET /api/v1/users/mixedcase
200 OK
{
"href" : "https://ambari-8d6c17ae32685572aa82f82b813138a1.cbdptest.com/api/v1/users/mixedcase",
"Users" : {
"active" : true,
"admin" : false,
"groups" : [ ],
"ldap_user" : false,
"user_name" : "mixedcase"
},
"widget_layouts" : [ ],
"privileges" : [ ]
}
{noformat}
Ambari should throw a 404 error at a minimum, but better yet, just lowercase the username requested and return the right user. Since we silently lowercase it on POST, we should do the same on GET, IMO.
was:
If you create a user with some capital letters in the username, Ambari accepts the request and creates a user with the lowercase version of that username. However, if you then do a GET on the original username, Ambari gives a 200 response but an empty response body:
{noformat}
GET /api/v1/users/MixedCase
<empty response>
GET /api/v1/users/mixedcase
{
"href" : "https://ambari-8d6c17ae32685572aa82f82b813138a1.cbdptest.com/api/v1/users/mixedcase",
"Users" : {
"active" : true,
"admin" : false,
"groups" : [ ],
"ldap_user" : false,
"user_name" : "mixedcase"
},
"widget_layouts" : [ ],
"privileges" : [ ]
}
{noformat}
Ambari should throw a 404 error at a minimum, but better yet, just lowercase the username requested and return the right user. Since we silently lowercase it on POST, we should do the same on GET, IMO.
> Creating a user with a mixed-case username behaves strangely
> ------------------------------------------------------------
>
> Key: AMBARI-14672
> URL: https://issues.apache.org/jira/browse/AMBARI-14672
> Project: Ambari
> Issue Type: Bug
> Reporter: Greg Hill
>
> If you create a user with some capital letters in the username, Ambari accepts the request and creates a user with the lowercase version of that username. However, if you then do a GET on the original username, Ambari gives a 200 response but an empty response body:
> {noformat}
> GET /api/v1/users/MixedCase
> 200 OK
> <empty response>
> GET /api/v1/users/mixedcase
> 200 OK
> {
> "href" : "https://ambari-8d6c17ae32685572aa82f82b813138a1.cbdptest.com/api/v1/users/mixedcase",
> "Users" : {
> "active" : true,
> "admin" : false,
> "groups" : [ ],
> "ldap_user" : false,
> "user_name" : "mixedcase"
> },
> "widget_layouts" : [ ],
> "privileges" : [ ]
> }
> {noformat}
> Ambari should throw a 404 error at a minimum, but better yet, just lowercase the username requested and return the right user. Since we silently lowercase it on POST, we should do the same on GET, IMO.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)