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] [Created] (ACCUMULO-4135) Change Kerberos impersonation configuration keys
Date Thu, 04 Feb 2016 16:45:39 GMT
Josh Elser created ACCUMULO-4135:
------------------------------------

             Summary: 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
             Fix For: 1.7.1, 1.8.0


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