[
https://issues.apache.org/jira/browse/MESOS-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16804270#comment-16804270
]
Andrei Sekretenko edited comment on MESOS-2842 at 3/28/19 8:13 PM:
-------------------------------------------------------------------
Discussed this with [~greggomann] - we decided that:
- to have both the ability to update principal and properly working
authorization is quite a nontrivial task
- it is not clear why would such an ability be needed at all
Therefore, I will stick to simply disallowing the framework to change its
principal.
At this point I have a local test that reproduces this issue, debugging that.
was (Author: asekretenko):
Discussed this with [~greggomann] - we decided that:
- to have both the ability to update principal and properly working
authorization is quite an nontrivial task
- it is not clear why would such an ability be needed at all
Therefore, I will stick to simply disallowing the framework to change its
principal.
At this point I have a local test that reproduces this issue, debugging that.
> Master crashes when framework changes principal on re-registration
> ------------------------------------------------------------------
>
> Key: MESOS-2842
> URL: https://issues.apache.org/jira/browse/MESOS-2842
> Project: Mesos
> Issue Type: Bug
> Reporter: Vinod Kone
> Assignee: Andrei Sekretenko
> Priority: Critical
> Labels: foundations, security
>
> The master should be updated to avoid crashing when a framework re-registers
> with a different principal.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
