Github user NeerajaRentachintala commented on the pull request:
https://github.com/apache/drill/pull/400#issuecomment-192382894
Folks
Why do we need to invent new terms here. What Drill is trying to here is a
very common use case for other tools in Hadoop eco system as well.
Can we just pick Hadoop terminology and move on.
-Neeraja
On Fri, Mar 4, 2016 at 7:23 AM, Keys Botzum <[email protected]>
wrote:
> One suggestion. The terms I use when discussing the concepts with
> customers are Drill inbound impersonation and Drill outbound
impersonation.
> That is absolutely clear. It does imply implementation to a bit but I
think
> makes intent very clear. You can then derive other terms from that such as
> "can_impersonate_inbound" and
> "principals_authorized_for_inbound_impersonation." Yea, really wording but
> very clear. We can of course shorten to "princ_auth_inbound_imper" in
code.
>
> Would that make sense?
>
> By the way the use of the termed chained in the context of security
> usually implied something like chained delegation which makes me think of
a
> security identity that is both end to end secure like kerberos and
includes
> all identities that were passed through. That's not this so I'd avoid use
> of the term chained.
>
> â
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/drill/pull/400#issuecomment-192320077>.
>
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
