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

Use a single ClientSession in ts_authorize

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      Currently a new ClientSession is created for every request sent to the REST server. However, it should be possible to use a single ClientSession for all requests. This would require setting the Authorization header every time the CSC authenticates itself with the REST server. This ticket is for implementing all that.

        Attachments

          Issue Links

            Activity

            Hide
            wvreeven Wouter van Reeven added a comment - - edited

            It turns out that custom headers can be set on any request (GET, POST, PUT) to the REST server. So a single ClientSession can be used and the Authorization header can be set as a parameter to the request.

            Show
            wvreeven Wouter van Reeven added a comment - - edited It turns out that custom headers can be set on any request (GET, POST, PUT) to the REST server. So a single ClientSession can be used and the Authorization header can be set as a parameter to the request.
            Hide
            wvreeven Wouter van Reeven added a comment -
            Show
            wvreeven Wouter van Reeven added a comment - ts_authorize PR: https://github.com/lsst-ts/ts_authorize/pull/20
            Hide
            rowen Russell Owen added a comment -

            Reviewed in github

            Show
            rowen Russell Owen added a comment - Reviewed in github

              People

              Assignee:
              wvreeven Wouter van Reeven
              Reporter:
              wvreeven Wouter van Reeven
              Reviewers:
              Russell Owen
              Watchers:
              Russell Owen, Wouter van Reeven
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.