[
https://issues.apache.org/jira/browse/NIFI-3193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16072685#comment-16072685
]
ASF GitHub Bot commented on NIFI-3193:
--------------------------------------
GitHub user m-hogue opened a pull request:
https://github.com/apache/nifi/pull/1971
NIFI-3193: added ability to authenticate using cert common names
This change allows for the PublishAMQP and ConsumeAMQP to use SSL cert
authentication instead of username/password. The change is backward compatible,
so it shouldn't affect anyone who plans to continue using SSL as a transport
_and_ username/password authentication.
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number
you are trying to resolve? Pay particular attention to the hyphen "-" character.
- [ ] Has your PR been rebased against the latest commit within the target
branch (typically master)?
- [ ] Is your initial contribution a single, squashed commit?
### For code changes:
- [ ] Have you ensured that the full suite of tests is executed via mvn
-Pcontrib-check clean install at the root nifi folder?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the LICENSE file, including the main
LICENSE file under nifi-assembly?
- [ ] If applicable, have you updated the NOTICE file, including the main
NOTICE file found under nifi-assembly?
- [ ] If adding new Properties, have you added .displayName in addition to
.name (programmatic access) for each of the new properties?
### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in
which it is rendered?
### Note:
Please ensure that once the PR is submitted, you check travis-ci for build
issues and submit an update to your PR as soon as possible.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/m-hogue/nifi NIFI-3193
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/1971.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1971
----
commit cd66c877b706b1f5b3418301e7e3aed651036bce
Author: m-hogue <[email protected]>
Date: 2017-06-27T20:19:10Z
NIFI-3193: added ability to authenticate using cert common names
----
> 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)
