[
https://issues.apache.org/jira/browse/NIFI-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15247072#comment-15247072
]
ASF GitHub Bot commented on NIFI-1197:
--------------------------------------
Github user joewitt commented on a diff in the pull request:
https://github.com/apache/nifi/pull/360#discussion_r60168086
--- Diff:
nifi-nar-bundles/nifi-mongodb-bundle/nifi-mongodb-processors/src/main/java/org/apache/nifi/processors/mongodb/AbstractMongoProcessor.java
---
@@ -52,6 +62,32 @@
.required(true)
.addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
.build();
+ public static final PropertyDescriptor SSL_CONTEXT_SERVICE = new
PropertyDescriptor.Builder()
+ .name("SSL Context Service")
+ .description("The SSL Context Service used to provide client
certificate information for TLS/SSL "
+ + "connections.")
+ .required(false)
+ .identifiesControllerService(SSLContextService.class)
+ .build();
+ public static final PropertyDescriptor CLIENT_AUTH = new
PropertyDescriptor.Builder()
+ .name("Client Auth")
--- End diff --
Not specific to this PR but rather this emerging guidance about machine
safety. We should encourage the use of displayName and better articulate the
difference between name and displayName. However, we should also be careful
suggesting 'this-is-for-robots' is anymore machine safe than 'This is for
Robots'.
> improve SSL options for getmongo and putmongo processor configuration
> properties
> --------------------------------------------------------------------------------
>
> Key: NIFI-1197
> URL: https://issues.apache.org/jira/browse/NIFI-1197
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Configuration
> Affects Versions: 0.3.0
> Reporter: subhash parise
>
> Hi Team,
> Now getmongo and putmongo configuration properties are mongodb URI,database
> name, collection name, etc, but if the mongodb server configured with the ssl
> it won't accept ssl options in mongodb uri.
> Could anyone please improve the ssl options in mongo proccessors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
