accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ACCUMULO-3874) Wrong username in exception when user doesn't exist
Date Mon, 01 Jun 2015 19:41:19 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Josh Elser resolved ACCUMULO-3874.
----------------------------------
    Resolution: Fixed

> Wrong username in exception when user doesn't exist
> ---------------------------------------------------
>
>                 Key: ACCUMULO-3874
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3874
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.7.0
>         Environment: Kerberos
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Minor
>             Fix For: 1.7.1, 1.8.0
>
>
> To get around the "/" in Kerberos principals, we base-64 encode the principals before
putting them in ZooKeeper.
> In the case where a user operation fails because that user doesn't exist (e.g. deleteuser),
the exception contains the base64-encoded name, not the actual kerberos principal.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message