accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-4135) Change Kerberos impersonation configuration keys
Date Sat, 06 Feb 2016 21:52:39 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15136024#comment-15136024
] 

ASF GitHub Bot commented on ACCUMULO-4135:
------------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/accumulo/pull/67


> Change Kerberos impersonation configuration keys
> ------------------------------------------------
>
>                 Key: ACCUMULO-4135
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4135
>             Project: Accumulo
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.7.0
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Blocker
>             Fix For: 1.7.1, 1.8.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> For the user impersonation support with Kerberos, we need to be able to represent the
following:
> For userA, what other users may userA "act" as and from what host(s) may userA do this
from.
> This was represented as the following in accumulo-site.xml:
> * {{<prefix>.userA.users}}=user1,user2,user3...
> * {{<prefix>.userA.hosts}}=fqdn1,fqdn2,fqdn3...
> Because we're dealing with Kerberos, "userA" is actually something like "primary/instance@REALM".
> I've recently found out that Ambari doesn't like this and apparently it would be prohibitively
difficult to change it there (urlencode, what?). I'll add some new configuration properties
here that change the structure so that there are options for users to configure this through
all deployment mechanisms.



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

Mime
View raw message