[
https://issues.apache.org/jira/browse/RANGER-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15662843#comment-15662843
]
Shi Wang commented on RANGER-696:
---------------------------------
Hi [~spolavarapu],
Thanks for reviewing the code.
1. I will add checking if new username exists to the patch.
2. Do you mean the condition in Ranger-1102? For Ranger-1102, I think we can
check if there is name conflict between internal and external user during user
sync and if there are any conflicts, pop up warning message and suggest user
change conflict internal username. Also I was thinking maybe we should only
allow changing internal user name.
It seems changing the external user name doesnt make much sense since if the
user name is unchanged in the source (like in AD) then it will sync the old
username again to database right?
3. For the UI scenario, currently we dont have ui support for changing user
name, but in the future if we do have this need to let user change username
from ui just like change password could reuse the code in this patch. The
solution I could think of is showing message in the ui ask user to relogin
after changing username.
And if use the python script to change username, maybe we can add restart
rangeradmin at the end so the logged in user will need relogin.
> 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
> Assignee: Shi Wang
> 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)
