You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Anand Mazumdar (JIRA)" <ji...@apache.org> on 2016/01/15 19:14:39 UTC

[jira] [Created] (MESOS-4398) Synchronously handle AuthZ errors for the Scheduler endpoint.

Anand Mazumdar created MESOS-4398:
-------------------------------------

             Summary: Synchronously handle AuthZ errors for the Scheduler endpoint.
                 Key: MESOS-4398
                 URL: https://issues.apache.org/jira/browse/MESOS-4398
             Project: Mesos
          Issue Type: Bug
    Affects Versions: 0.25.0
            Reporter: Anand Mazumdar


Currently, any AuthZ errors for the {{/scheduler}} endpoint are handled asynchronously as {{FrameworkErrorMessage}}. Here is an example:

{code}
  if (authorizationError.isSome()) {
    LOG(INFO) << "Refusing subscription of framework"
              << " '" << frameworkInfo.name() << "'"
              << ": " << authorizationError.get().message;

    FrameworkErrorMessage message;
    message.set_message(authorizationError.get().message);
    http.send(message);
    http.close();
    return;
  }
{code}

We would like to handle such errors synchronously when the request is received similar to what other endpoints like {{/reserve}}/{{/quota}} do. We already have the relevant functions {{authorizeXXX}} etc in {{master.cpp}}. We should just make the requests pass through once the relevant {{Future}} from the {{authorizeXXX}} function is fulfilled.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)