[
https://issues.apache.org/jira/browse/STORM-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14086661#comment-14086661
]
ASF GitHub Bot commented on STORM-349:
--------------------------------------
Github user revans2 commented on the pull request:
https://github.com/apache/incubator-storm/pull/215#issuecomment-51250810
Overall it looks good. I think in the future we probably want to explore
allowing the UI to pretend to be a different user to nimbus. This would make
the code a lot simpler, and would open up a number of other possibilities in
the future.
We could try to do this by modifying the SASL negotiation that happens when
authenticating the connection, but I think it would be simpler to update the
different Thrift operations to optionally include a doAs argument. Then Nimbus
would validate that the real user is authorized to perform operations on behalf
of other users and update things accordingly. Perhaps you could file a JIRA
for this.
> (Security) ui actions should have nimbus like authroization
> -----------------------------------------------------------
>
> Key: STORM-349
> URL: https://issues.apache.org/jira/browse/STORM-349
> Project: Apache Storm (Incubating)
> Issue Type: Bug
> Reporter: Robert Joseph Evans
> Assignee: Sriharsha Chintalapani
> Labels: security
>
> The UI provides APIs to kill, rebalance, ... a topology. For security we
> originally took the route to optionally disable these, but ideally the UI
> server would load an IAuthorizer instance like nimbus, and check if the user
> is allowed to perform that operation before doing it on behalf of the user.
> This should be fairly straight forward but may require some glue code like is
> being used in the drpc server for its web interface.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
