-
Type: Bug
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: 10.10-HF54, 2021.11
-
Fix Version/s: 10.10-HF56, 2021.13
-
Component/s: S3
-
Tags:
-
Backlog priority:1,000
-
Sprint:nxplatform #50
-
Story Points:2
Since NXP-28162, it's possible to use a custom S3 configuration to build a SSL context. However if this custom S3 configuration does not define the nuxeo.aws.*Store* props, it will cause a NPE like
ERROR [main] [org.nuxeo.runtime.model.ComponentManager] Component service:org.nuxeo.ecm.automation.server.BatchManager notification of application started failed: null java.lang.NullPointerException: null at org.nuxeo.runtime.aws.AWSConfigurationServiceImpl.getSSLContext(AWSConfigurationServiceImpl.java:115) ~[nuxeo-runtime-aws-10.10-HF54.jar:?] at org.nuxeo.runtime.aws.AWSConfigurationServiceImpl.configureSSL(AWSConfigurationServiceImpl.java:106) ~[nuxeo-runtime-aws-10.10-HF54.jar:?] at org.nuxeo.runtime.aws.AWSConfigurationService.configureSSL(AWSConfigurationService.java:57) ~[nuxeo-runtime-aws-10.10-HF54.jar:?] at org.nuxeo.ecm.core.storage.sql.S3BinaryManager.setupCloudClient(S3BinaryManager.java:321) ~[nuxeo-core-binarymanager-s3-10.10-HF54.jar:?] at org.nuxeo.ecm.blob.AbstractCloudBinaryManager.initialize(AbstractCloudBinaryManager.java:121) ~[nuxeo-core-binarymanager-common-10.10-HF48.jar:?]
- is caused by
-
NXP-28162 Allow configuration of custom S3 truststore
- Resolved
- Is referenced in