[jira] [Commented] (NIFI-3193) Update ConsumeAMQP and PublishAMQP to retrieve username from certificate common name

["Brian (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-3193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071729#comment-16071729 ] 

Brian commented on NIFI-3193:
-----------------------------

[~m-hogue] I've compiled and tested your change and it works a treat. I was using RabbitmQ 3.4.2 and Erlang 18.0 and I was able to successfully publish and consume using only SSL certificates.

In reference to the queue declaration I think your absolutly right that should be left to the admins and doesn't need to be handled within the NiFi processor.

> 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)