[
https://issues.apache.org/jira/browse/NIFI-3193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16073875#comment-16073875
]
ASF GitHub Bot commented on NIFI-3193:
--------------------------------------
Github user m-hogue commented on a diff in the pull request:
https://github.com/apache/nifi/pull/1971#discussion_r125505285
--- Diff:
nifi-nar-bundles/nifi-amqp-bundle/nifi-amqp-processors/src/main/java/org/apache/nifi/amqp/processors/AMQPPublisher.java
---
@@ -16,14 +16,14 @@
*/
package org.apache.nifi.amqp.processors;
-import java.io.IOException;
-
-import org.apache.nifi.logging.ComponentLog;
--- End diff --
Yeah, I'll make sure to avoid this in the future as well
> 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)
