[
https://issues.apache.org/jira/browse/RANGER-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15340975#comment-15340975
]
Velmurugan Periasamy commented on RANGER-1039:
----------------------------------------------
Patch committed to master -
https://git-wip-us.apache.org/repos/asf?p=incubator-ranger.git;a=commit;h=04378e386793180c61d1167f168b6aad9620d179
> User and groups having special characters are not populating in edit policy
> page
> --------------------------------------------------------------------------------
>
> Key: RANGER-1039
> URL: https://issues.apache.org/jira/browse/RANGER-1039
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Affects Versions: 0.5.0, 0.6.0
> Reporter: Pradeep Agrawal
> Assignee: Pradeep Agrawal
> Fix For: 0.6.0
>
> Attachments: RANGER-1039-1.patch
>
>
> Problem statement : User and groups having special characters are not
> populating
> in edit policy page.
> Example Case : Ranger admin behavior for username usu+gonzáev
> While loading Edit policy page; each user details are requested using
> userSearch API by sending username as search filter.
> observed REST request was :
> http://localhost:6080/service/xusers/users?page=0&pageSize=25&startIndex=0&name=usu%2Bgonz%C3%A1ev
> At Ranger admin end when request was received; username was received as :
> usu+gonzáev
> To fetch user details; generated Sql query was : SELECT COUNT(ID) FROM x_user
> WHERE ((1 = 1) AND LOWER(USER_NAME) LIKE '%usu+gonz??ev%')
> Above SQL query didn't returned any row as provided username did not matches
> with available username in db; in DB username entry was observed as :
> 'usu+gonz�ev'
> REST call returned response code 200 with no records; UI end code did not get
> any response object so it got stuck there.
> Proposed Solution : Rather using user search api; search by username api can
> be used to avoid encoded character addition.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
