[
https://issues.apache.org/jira/browse/RANGER-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15634361#comment-15634361
]
Shi Wang commented on RANGER-696:
---------------------------------
The solution in patch 0001-RANGER-696-Option-to-use-custom-admin-username.patch
is not specific to admin user.
We can use security-admin/scripts/changeusernameutil.py to change any user's
username, as long as we know the old user name and password.
The usage is changeusernameutil.py <loginuser_id> <password> <new_username>
If the old username(loginuserid) cannot be found in database or password not
correct, or new username is the same with old username it will not proceed to
change username.
> Option to use custom "admin" username
> -------------------------------------
>
> Key: RANGER-696
> URL: https://issues.apache.org/jira/browse/RANGER-696
> Project: Ranger
> Issue Type: Improvement
> Components: admin
> Affects Versions: 0.5.1
> Reporter: Don Bosco Durai
> Fix For: 0.7.0
>
> Attachments: 0001-RANGER-696-Option-to-use-custom-admin-username.patch
>
>
> It would be good to allow customization of Admin username other than "admin".
> The reason being, in some environment, there might be another user called
> "admin" and that might conflict with Ranger "admin" user.
> Giving an option to set another name or exclude external synchronization of
> user with "admin" will be useful.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
