Details

    • Type: Task
    • Status: Resolved
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      There's a large overlap in users of Marathon and Chronos. It'd reduce operational complexity for everyone using both if we could find a way to work with Chronos to have shared auth. Benefits of having just one place to store credentials include making it easier to manage when an employee joins or leaves the company, easier password changes, easier to create auth plugins (e.g. I thought it might be interesting to implement SAML support so mesos could be used with OneLogin and similar services) This could be a shared library that both use or some other solution. Both projects have many of the same users and same committers (e.g. [~ssorallen] and [~florianleibert] are top committers of both), so I think this could be feasible. I'm not involved in either project and realize the difficulties of coordinating across projects, but it could be interesting to discuss. I've opened this issue on the Chronos project as well (https://github.com/airbnb/chronos/issues/190)

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              GitHub_benmccann Ben McCann (Inactive)
              Team:
              Orchestration Team
              Watchers:
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: