Uploaded image for project: 'Puppet Server'
  1. Puppet Server
  2. SERVER-111

auth.conf replacement

    XMLWordPrintable

    Details

    • Type: Epic
    • Status: Closed
    • Priority: Normal
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: SERVER 2.2.0
    • Component/s: None
    • Labels:
      None
    • Epic Name:
      Green: auth.conf replacement
    • Template:
    • Team/s:
      Organizational Scale
    • Sub-team:
    • Epic Status:
      Done

      Description

      For endpoints that live directly on the clojure side of the fence, we don't run them through the existing auth.conf ruby code to handle authorization. This means that any endpoints that do require authorization need to have their own special settings created for them, which is not a good long-term solution. Instead, we should come up with a general solution that can be used across all of the future endpoints. Hopefully this ends up being some ring middleware that can be re-used in many places and reads from a well-known config file/format.

      We should also probably discuss whether or not it would make sense to look into integrating with the RBAC service.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              chris Chris Price
              QA Contact:
              Erik Dasher
              UX Contact:
              JD Welch
              Votes:
              2 Vote for this issue
              Watchers:
              18 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support