Uploaded image for project: 'Artifactory Binary Repository'
  1. Artifactory Binary Repository
  2. RTFACT-12957

Jets3t binary provider doesn't use custom properties with the signature-based S3 service

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: High
    • Resolution: Fixed
    • Affects Version/s: 4.14.2
    • Fix Version/s: 6.4.0
    • Component/s: S3
    • Labels:
      None

      Description

      TL;DR
      JetS3t properties (user defined properties) are ignored when <useSignature> is set to true. Read on for more details.

      When <useSignature> is set to true, Artifactory initializes an additional RestS3Service and uses it to send signed requests to AWS (exists, add, get, delete all use this object). The problem is that we're not initializing it properly and the custom props that should be injected using the binarystore.xml are only preserved with one of the RestS3Service objects (not the one that's used to send signed requests).

      This has implications on various things such as SSE (server side encryption), which can't be used when using signed requests, and other properties which aren't effective (such as s3 connection pool size, etc)

        Attachments

          Activity

            People

            • Assignee:
              yuvalr Yuval Reches
              Reporter:
              uriahl Uriah Levy
              Assigned QA:
              Konstantin Shenderov
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: