[RTFACT-12957] Jets3t binary provider doesn't use custom properties with the signature-based S3 service Created: 07/Dec/16  Updated: 20/Sep/18  Resolved: 20/Sep/18

Status: Resolved
Project: Artifactory Binary Repository
Component/s: S3
Affects Version/s: 4.14.2
Fix Version/s: 6.4.0

Type: Bug Priority: High
Reporter: Uriah Levy Assignee: Yuval Reches
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Assigned QA: Konstantin Shenderov (Inactive)


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)

Generated at Tue Apr 07 07:19:13 UTC 2020 using Jira 8.5.3#805003-sha1:b4933e02eaff29a49114274fe59e1f99d9d963d7.