Uploaded image for project: 'jclouds'
  1. jclouds
  2. JCLOUDS-255

atmos, aws-s3, azure blob signers doesn't support query parameter authentication

    XMLWordPrintableJSON

    Details

      Description

      Some blob store providers allow using signed requests in two forms: either with an Authorization header or with query parameters. Using the query parameter form of the signed request is necessary for clients that don't support adding a header or for returning a redirect where the Authorization header would be removed.

      The jclouds atmos, aws-s3, and azure implementations generate signed requests only with the Authorization header, while cloudfiles-us, hpcloud-objectstorage use query parameters. Ideally the BlobRequestSigner interface would allow the user to decide which form of signed request to create.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                gaul Andrew Gaul
                Reporter:
                kevin.krouse Kevin Krouse
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: