[
https://issues.apache.org/jira/browse/NIFI-3193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16074902#comment-16074902
]
ASF GitHub Bot commented on NIFI-3193:
--------------------------------------
Github user trkurc commented on a diff in the pull request:
https://github.com/apache/nifi/pull/1971#discussion_r125669424
--- Diff:
nifi-nar-bundles/nifi-amqp-bundle/nifi-amqp-processors/src/main/resources/docs/org.apache.nifi.amqp.processors.ConsumeAMQP/additionalDetails.html
---
@@ -63,6 +63,9 @@
<li><b>Password</b> - [REQUIRED] password to use with user name to
connect to AMQP broker.
Usually provided by the administrator. Defaults to 'guest'.
</li>
+ <li><b>Cert Authentication</b> - [OPTIONAL] whether or not to use the
SSL certificate for authentication rather than user name and password.
--- End diff --
Would it be possible to have this match the displayName text?
> Update ConsumeAMQP and PublishAMQP to retrieve username from certificate
> common name
> ------------------------------------------------------------------------------------
>
> Key: NIFI-3193
> URL: https://issues.apache.org/jira/browse/NIFI-3193
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Affects Versions: 1.0.0, 1.1.0, 0.7.1
> Reporter: Brian
> Assignee: Michael Hogue
>
> At the moment the NiFi AMQP processors can establish a SSL connection to
> RabbitMQ but still user a user defined username and password to authenticate.
> When using certificates RabbitMQ allows you to use to COMMON_NAME from the
> certificate to authenticate instead of providing a username and password.
> Unfortunately the NiFi processors do not support this so I would like to
> request an update to the processors to enable this functionality.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
