[
https://issues.apache.org/jira/browse/ACCUMULO-4492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Tubbs resolved ACCUMULO-4492.
-----------------------------------------
Resolution: Abandoned
Closing this old issue. If this is still a problem, please open a new issue or
PR at https://github.com/apache/accumulo
> operations tool to migrate existing users when enabling Kerberos
> ----------------------------------------------------------------
>
> Key: ACCUMULO-4492
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4492
> Project: Accumulo
> Issue Type: New Feature
> Reporter: Sean Busbey
> Priority: Major
>
> When converting an existing cluster to use Kerberos, existing user
> permissions aren't much use unless the user names happen to be formatted like
> Kerberos principals.
> An offline tool that folks migrating can use to map existing user names to
> principals would be super useful.
> Essentially something like:
> {code}
> $ accumulo kerberos-migration --include-users=* --exclude-users=root
> --no-instance --realm=EXAMPLE.COM
> Migrating users matching '*' and not matching 'root'.
> User principals will not have an instance component.
> User principals will be in the realm 'EXAMPLE.COM'
> Found user 'auser', converted to 'au...@example.com'
> Found user 'another_user', converted to 'another_u...@example.com'
> Found user 'hpnewton', converted to 'hpnew...@example.com'
> Found user 'root', skipped due to exclusion rule
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
