[
https://issues.apache.org/jira/browse/AURORA-687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15061146#comment-15061146
]
R.B. Boyer edited comment on AURORA-687 at 12/16/15 11:40 PM:
--------------------------------------------------------------
Bump? This is blocking further adoption of Aurora for us, as we use the mesos
master ACL authorization facilities for our existing frameworks and are
reluctant to disable those security features just for Aurora.
Also it looks like the prior reviewboard patch already got a "ship it" so this
seems like all it needs is a merge to master.
was (Author: naelyn):
Bump? This is blocking further adoption of Aurora for us, as we use the mesos
master ACL authorization facilities for our existing frameworks and are
reluctant to disable those security features just for Aurora.
> Aurora should set FrameworkInfo.principal
> -----------------------------------------
>
> Key: AURORA-687
> URL: https://issues.apache.org/jira/browse/AURORA-687
> Project: Aurora
> Issue Type: Task
> Reporter: Zameer Manji
> Priority: Minor
>
> The principal field has been in FrameworkInfo since 0.19. In 0.20 it will be
> used for authorization and rate limiting. We should set this field so we can
> use those features.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
