Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-4552

Design the authorization management through or around Butler

    Details

    • Type: Story
    • Status: To Do
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: butler
    • Labels:
      None
    • Templates:
    • Team:
      Data Access and Database

      Description

      We need to understand how authentication information is passed through or around the Butler to background services it may access.

      per Paul Price If butler uses authorization, the auth must be able to be passed between instances of butler; current use case is to pickle butler, send it to another process, and unpickle. It is possible we will choose another serialization or re-instantiation (such as instantiate-from-configuration) scheme, but whatever we choose the auth must be able to be used by the 2nd (and so forth) instantiated butler.

        Attachments

          Container Issues

            Issue Links

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  npease Nate Pease
                  Watchers:
                  Alexander Withers [X] (Inactive), Brian Van Klaveren, Daniel Thayer [X] (Inactive), Jacek Becla, James Basney, Nate Pease, Terry Fleury [X] (Inactive)
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  7 Start watching this issue

                  Dates

                  • Created:
                    Updated:

                    Summary Panel