[
https://issues.apache.org/jira/browse/STORM-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14334441#comment-14334441
]
Parth Brahmbhatt commented on STORM-446:
----------------------------------------
[~harsha_ch] I haven't thought this through but my initial impression is that
will be a pretty fat API taking way too many optional params and will be hard
to use. We don't really have to pass the credentials of the other user, just
the principal name. The reason I was hoping to find a way to have another
principal submitted was because I stumbled upon
http://docs.oracle.com/javase/7/docs/api/javax/security/sasl/AuthorizeCallback.html
which seems to talk about authenticated and authrozied ids and also has a
method isAuthorized() that determines if autheticatedId can act on behalf of
authorizedId. I could not find any useful examples or any documentation other
than java doc.
If there is indeed no way to pass any additional info, I can add the API you
suggested or add the optional doAs param to all APIs.
[~revans2] [~ptgoetz] any thoughts?
> secure Impersonation in storm
> -----------------------------
>
> Key: STORM-446
> URL: https://issues.apache.org/jira/browse/STORM-446
> Project: Apache Storm
> Issue Type: Improvement
> Reporter: Sriharsha Chintalapani
> Assignee: Parth Brahmbhatt
> Labels: Security
>
> Storm security adds features of authenticating with kerberos and than uses
> that principal and TGT as way to authorize user operations, topology
> operation. Currently Storm UI user needs to be part of nimbus.admins to get
> details on user submitted topologies. Ideally storm ui needs to take
> authenticated user principal to submit requests to nimbus which will than
> authorize the user rather than storm UI user. This feature will also benefit
> superusers to impersonate other users to submit topologies in a secured way.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
