You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Tony Kurc (JIRA)" <ji...@apache.org> on 2017/07/05 19:34:00 UTC

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

     [ https://issues.apache.org/jira/browse/NIFI-3193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tony Kurc resolved NIFI-3193.
-----------------------------
    Resolution: Fixed

> 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
>             Fix For: 1.4.0
>
>
> 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)