Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-27805

S3BinaryManager: allow configurable digest

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 9.10, 10.10
    • Fix Version/s: 9.10-HF37, 10.10-HF15, 11.1
    • Component/s: S3
    • Release Notes Summary:
      The digest algorithm is configurable for S3 storage.
    • Tags:
    • Backlog priority:
      600
    • Impact type:
      Configuration Change
    • Upgrade notes:
      Hide

      The digest algorithm to use to compute a unique key when storing blobs in S3 can now be configured, using:

      nuxeo.s3storage.digest=SHA-256
      

      Or if full XML configuration is used (necessary if there are several different S3 blob providers):

      <extension target="org.nuxeo.ecm.core.blob.BlobManager" point="configuration">
        <blobprovider name="default">
          <class>org.nuxeo.ecm.core.storage.sql.S3BinaryManager</class>
          ...
          <property name="digest">SHA-256</property>
          ...
        </blobprovider>
      </extension>
      

      The default is MD5. The valid digest algorithms are those available to the Java runtime, the standard ones are listed here for Java 8 and here for Java 11.

      Show
      The digest algorithm to use to compute a unique key when storing blobs in S3 can now be configured, using: nuxeo.s3storage.digest=SHA-256 Or if full XML configuration is used (necessary if there are several different S3 blob providers): <extension target= "org.nuxeo.ecm.core.blob.BlobManager" point= "configuration" > <blobprovider name= "default" > <class> org.nuxeo.ecm.core.storage.sql.S3BinaryManager </class> ... <property name= "digest" > SHA-256 </property> ... </blobprovider> </extension> The default is MD5 . The valid digest algorithms are those available to the Java runtime, the standard ones are listed here for Java 8 and here for Java 11 .
    • Sprint:
      nxsupport 11.1.4, nxFG 11.1.10

      Description

      Currently we can not configure the S3BinaryManager to work with other hashes like SHA-1, SHA-2, SHA-3.  This improvement request is to support a configurable digest for the S3BinaryManager like we can with the DefaultBinaryManager.

       

      Note: There are some hard coded references to MD5 as a digest algorithm in S3BinaryManager, see fetchFile method.

       

       

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 0 minutes
                  0m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 3 hours
                  3h

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.