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

Allow configuration of custom S3 truststore

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 10.10
    • Fix Version/s: 10.10-HF54, 2021.11
    • Component/s: S3
    • Release Notes Summary:
      New configuration properties have been added to allow the configuration of a custom S3 truststore.
    • Backlog priority:
      900
    • Upgrade notes:
      Hide

      New configuration properties have been added to allow the configuration of a custom S3 truststore:

      nuxeo.aws.trustStorePath=
      nuxeo.aws.trustStorePassword=
      nuxeo.aws.trustStoreType=
      nuxeo.aws.keyStorePath=
      nuxeo.aws.keyStorePassword=
      nuxeo.aws.keyStoreType=
      
      Show
      New configuration properties have been added to allow the configuration of a custom S3 truststore: nuxeo.aws.trustStorePath= nuxeo.aws.trustStorePassword= nuxeo.aws.trustStoreType= nuxeo.aws.keyStorePath= nuxeo.aws.keyStorePassword= nuxeo.aws.keyStoreType=
    • Sprint:
      nxplatform #44, nxplatform #45, nxplatform #46
    • Story Points:
      2

      Description

      The same way MongoDB implementation allows to use a truststore different from the JVM one to initialize the SSL context, the S3 implementation should allow the same configuration, which would be specifically interesting if a self-signed CA is used.

      The implementation could follow what is described in
      https://stackoverflow.com/questions/28084399/amazon-s3-sdk-for-java-configure-tlsv1-2#28094222

        Attachments

        1. aws-config.xml.nxftl
          2 kB
          Nour Al Kotob
        2. nuxeo.defaults
          0.3 kB
          Nour Al Kotob

          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 - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 2 days, 3 hours
                  2d 3h