[jira] [Updated] (MESOS-5730) Sandbox access authorization should fail for non existing sandboxes.
[
https://issues.apache.org/jira/browse/MESOS-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Harutyunyan updated MESOS-5730:
-
Sprint: Mesosphere Sprint 38 (was: Mesosphere Sprint 38, Mesosphere Sprint
39)
> Sandbox access authorization should fail for non existing sandboxes.
>
>
> Key: MESOS-5730
> URL: https://issues.apache.org/jira/browse/MESOS-5730
> Project: Mesos
> Issue Type: Bug
> Components: security
>Affects Versions: 1.0.0
>Reporter: Till Toenshoff
> Labels: authorization, mesosphere, security
>
> The local authorizer currently tries to authorize {{ACCESS_SANDBOX}} even if
> no further object specification - e.g. {{framework_info}} or
> {{executor_info}}) where specified / available at that time.
> Given that there is likely no sandbox available if there was no
> {{executor_info}} provided, I think we should actually fail instead of allow
> or deny (403).
> A failure would result into an IMHO more appropriate ServiceUnavailable
> (503).
> See
> https://github.com/apache/mesos/commit/c8d67590064e35566274116cede9c6a733187b48#diff-dd692b1640b2628014feca01a94ba1e1R241
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-5730) Sandbox access authorization should fail for non existing sandboxes.
[
https://issues.apache.org/jira/browse/MESOS-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Harutyunyan updated MESOS-5730:
-
Sprint: Mesosphere Sprint 38, Mesosphere Sprint 39 (was: Mesosphere Sprint
38)
> Sandbox access authorization should fail for non existing sandboxes.
>
>
> Key: MESOS-5730
> URL: https://issues.apache.org/jira/browse/MESOS-5730
> Project: Mesos
> Issue Type: Bug
> Components: security
>Affects Versions: 1.0.0
>Reporter: Till Toenshoff
> Labels: authorization, mesosphere, security
>
> The local authorizer currently tries to authorize {{ACCESS_SANDBOX}} even if
> no further object specification - e.g. {{framework_info}} or
> {{executor_info}}) where specified / available at that time.
> Given that there is likely no sandbox available if there was no
> {{executor_info}} provided, I think we should actually fail instead of allow
> or deny (403).
> A failure would result into an IMHO more appropriate ServiceUnavailable
> (503).
> See
> https://github.com/apache/mesos/commit/c8d67590064e35566274116cede9c6a733187b48#diff-dd692b1640b2628014feca01a94ba1e1R241
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-5730) Sandbox access authorization should fail for non existing sandboxes.
[
https://issues.apache.org/jira/browse/MESOS-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam B updated MESOS-5730:
--
Fix Version/s: (was: 1.0.0)
> Sandbox access authorization should fail for non existing sandboxes.
>
>
> Key: MESOS-5730
> URL: https://issues.apache.org/jira/browse/MESOS-5730
> Project: Mesos
> Issue Type: Bug
> Components: security
>Affects Versions: 1.0.0
>Reporter: Till Toenshoff
> Labels: authorization, mesosphere, security
>
> The local authorizer currently tries to authorize {{ACCESS_SANDBOX}} even if
> no further object specification - e.g. {{framework_info}} or
> {{executor_info}}) where specified / available at that time.
> Given that there is likely no sandbox available if there was no
> {{executor_info}} provided, I think we should actually fail instead of allow
> or deny (403).
> A failure would result into an IMHO more appropriate ServiceUnavailable
> (503).
> See
> https://github.com/apache/mesos/commit/c8d67590064e35566274116cede9c6a733187b48#diff-dd692b1640b2628014feca01a94ba1e1R241
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-5730) Sandbox access authorization should fail for non existing sandboxes.
[
https://issues.apache.org/jira/browse/MESOS-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Toenshoff updated MESOS-5730:
--
Priority: Major (was: Blocker)
> Sandbox access authorization should fail for non existing sandboxes.
>
>
> Key: MESOS-5730
> URL: https://issues.apache.org/jira/browse/MESOS-5730
> Project: Mesos
> Issue Type: Bug
> Components: security
>Affects Versions: 1.0.0
>Reporter: Till Toenshoff
> Labels: authorization, mesosphere, security
> Fix For: 1.0.0
>
>
> The local authorizer currently tries to authorize {{ACCESS_SANDBOX}} even if
> no further object specification - e.g. {{framework_info}} or
> {{executor_info}}) where specified / available at that time.
> Given that there is likely no sandbox available if there was no
> {{executor_info}} provided, I think we should actually fail instead of allow
> or deny (403).
> A failure would result into an IMHO more appropriate ServiceUnavailable
> (503).
> See
> https://github.com/apache/mesos/commit/c8d67590064e35566274116cede9c6a733187b48#diff-dd692b1640b2628014feca01a94ba1e1R241
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-5730) Sandbox access authorization should fail for non existing sandboxes.
[
https://issues.apache.org/jira/browse/MESOS-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam B updated MESOS-5730:
--
Component/s: security
> Sandbox access authorization should fail for non existing sandboxes.
>
>
> Key: MESOS-5730
> URL: https://issues.apache.org/jira/browse/MESOS-5730
> Project: Mesos
> Issue Type: Bug
> Components: security
>Affects Versions: 1.0.0
>Reporter: Till Toenshoff
>Priority: Blocker
> Labels: authorization, mesosphere, security
> Fix For: 1.0.0
>
>
> The local authorizer currently tries to authorize {{ACCESS_SANDBOX}} even if
> no further object specification - e.g. {{framework_info}} or
> {{executor_info}}) where specified / available at that time.
> Given that there is likely no sandbox available if there was no
> {{executor_info}} provided, I think we should actually fail instead of allow
> or deny (403).
> A failure would result into an IMHO more appropriate ServiceUnavailable
> (503).
> See
> https://github.com/apache/mesos/commit/c8d67590064e35566274116cede9c6a733187b48#diff-dd692b1640b2628014feca01a94ba1e1R241
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-5730) Sandbox access authorization should fail for non existing sandboxes.
[
https://issues.apache.org/jira/browse/MESOS-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam B updated MESOS-5730:
--
Sprint: Mesosphere Sprint 38
> Sandbox access authorization should fail for non existing sandboxes.
>
>
> Key: MESOS-5730
> URL: https://issues.apache.org/jira/browse/MESOS-5730
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Till Toenshoff
>Priority: Blocker
> Labels: authorization, mesosphere, security
> Fix For: 1.0.0
>
>
> The local authorizer currently tries to authorize {{ACCESS_SANDBOX}} even if
> no further object specification - e.g. {{framework_info}} or
> {{executor_info}}) where specified / available at that time.
> Given that there is likely no sandbox available if there was no
> {{executor_info}} provided, I think we should actually fail instead of allow
> or deny (403).
> A failure would result into an IMHO more appropriate ServiceUnavailable
> (503).
> See
> https://github.com/apache/mesos/commit/c8d67590064e35566274116cede9c6a733187b48#diff-dd692b1640b2628014feca01a94ba1e1R241
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-5730) Sandbox access authorization should fail for non existing sandboxes.
[
https://issues.apache.org/jira/browse/MESOS-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Toenshoff updated MESOS-5730:
--
Description:
The local authorizer currently tries to authorize {{ACCESS_SANDBOX}} even if no
further object specification - e.g. {{framework_info}} or {{executor_info}})
where specified / available at that time.
Given that there is likely no sandbox available if there was no
{{executor_info}} provided, I think we should actually fail instead of allow or
deny (403).
A failure would result into an IMHO more appropriate ServiceUnavailable (503).
See
https://github.com/apache/mesos/commit/c8d67590064e35566274116cede9c6a733187b48#diff-dd692b1640b2628014feca01a94ba1e1R241
was:
The local authorizer currently tries to authorize {{ACCESS_SANDBOX}} even if no
further object specification - e.g. {{framework_info}} or {{executor_info}})
where specified / available at that time.
Given that there is likely no sandbox available if there was no
{{executor_info}} provided, I think we should actually fail instead of deny
(403).
A failure would result into an IMHO more appropriate ServiceUnavailable (503).
See
https://github.com/apache/mesos/commit/c8d67590064e35566274116cede9c6a733187b48#diff-dd692b1640b2628014feca01a94ba1e1R241
> Sandbox access authorization should fail for non existing sandboxes.
>
>
> Key: MESOS-5730
> URL: https://issues.apache.org/jira/browse/MESOS-5730
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Till Toenshoff
>Priority: Blocker
> Labels: authorization, mesosphere, security
> Fix For: 1.0.0
>
>
> The local authorizer currently tries to authorize {{ACCESS_SANDBOX}} even if
> no further object specification - e.g. {{framework_info}} or
> {{executor_info}}) where specified / available at that time.
> Given that there is likely no sandbox available if there was no
> {{executor_info}} provided, I think we should actually fail instead of allow
> or deny (403).
> A failure would result into an IMHO more appropriate ServiceUnavailable
> (503).
> See
> https://github.com/apache/mesos/commit/c8d67590064e35566274116cede9c6a733187b48#diff-dd692b1640b2628014feca01a94ba1e1R241
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-5730) Sandbox access authorization should fail for non existing sandboxes.
[
https://issues.apache.org/jira/browse/MESOS-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Toenshoff updated MESOS-5730:
--
Affects Version/s: 1.0.0
> Sandbox access authorization should fail for non existing sandboxes.
>
>
> Key: MESOS-5730
> URL: https://issues.apache.org/jira/browse/MESOS-5730
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Till Toenshoff
>Priority: Blocker
> Labels: authorization, mesosphere, security
> Fix For: 1.0.0
>
>
> The local authorizer currently tries to authorize {{ACCESS_SANDBOX}} even if
> no further object specification - e.g. {{framework_info}} or
> {{executor_info}}) where specified / available at that time.
> Given that there is likely no sandbox available if there was no
> {{executor_info}} provided, I think we should actually fail instead of deny
> (403).
> A failure would result into an IMHO more appropriate ServiceUnavailable
> (503).
> See
> https://github.com/apache/mesos/commit/c8d67590064e35566274116cede9c6a733187b48#diff-dd692b1640b2628014feca01a94ba1e1R241
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
