[GitHub] nifi issue #3009: NIFI-4532 OpenID Connect User Authentication
Github user SarthakSahu commented on the issue: https://github.com/apache/nifi/pull/3009 @apiri could you please delegate this to somebody for review. ---
[GitHub] nifi issue #2866: NIFI-4710 Kerberos support for user auth in Docker instanc...
Github user SarthakSahu commented on the issue: https://github.com/apache/nifi/pull/2866 I had configure my own KDCD server and followed https://bryanbende.com/development/2016/08/31/apache-nifi-1.0.0-kerberos-authentication. Please have a look on this. ---
[GitHub] nifi issue #3009: NIFI-4532 OpenID Connect User Authentication
Github user SarthakSahu commented on the issue: https://github.com/apache/nifi/pull/3009 @apiri could you please delegate this to somebody for review. ---
[GitHub] nifi pull request #3009: NIFI-4532 OpenID Connect User Authentication
GitHub user SarthakSahu opened a pull request: https://github.com/apache/nifi/pull/3009 NIFI-4532 OpenID Connect User 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- where 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/SarthakSahu/nifi NIFI-4532 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/3009.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 #3009 commit cfc5a4b4e85e5d90d45d079f6ec46a135d0e2d61 Author: Sahu Sarthak Date: 2018-09-16T16:51:25Z NIFI-4532 OpenID Connect User Authentication ---
[GitHub] nifi issue #2866: NIFI-4710 Kerberos support for user auth in Docker instanc...
Github user SarthakSahu commented on the issue: https://github.com/apache/nifi/pull/2866 @pepov PR is ready with spnego enhancement and updated last review comments. Please review it. ---
[GitHub] nifi issue #2866: NIFI-4710 Kerberos support for user auth in Docker instanc...
Github user SarthakSahu commented on the issue: https://github.com/apache/nifi/pull/2866 @pepov I am just trying to configure the environment for spnego testing. Once I can able to test it, will inform for review. ---
[GitHub] nifi issue #2866: NIFI-4710 Kerberos support for user auth in Docker instanc...
Github user SarthakSahu commented on the issue: https://github.com/apache/nifi/pull/2866 @pepov ok. 1. Service Principal and service keytab required where as nifi needs authenticate as client. So when nifi needs to authenticate as client to kerborized zookeeper service keytab and principal is needed. 2. For user authentication nifi will authenticate users with help of KDC server. For example: A "pepov" user wants to authenticate with nifi. We need to create a principal in KDC server as pe...@example.com using below command. Note: we have not used -randkey option. Instead we provide password to the created princpal kadmin: addprinc pepov WARNING: no policy specified for pe...@example.com; defaulting to no policy Enter password for principal "pe...@example.com": Re-enter password for principal "pe...@example.com": Principal "pe...@example.com" created. Now we have to provide the username(pepov) and password in the login page to access nifi. Hope this clarify the query. ---
[GitHub] nifi issue #2866: NIFI-4710 Kerberos support for user auth in Docker instanc...
Github user SarthakSahu commented on the issue: https://github.com/apache/nifi/pull/2866 @pepov This Jira is only for user authentication through Kerberos. So kerebros zookeeper support has not provided here. ---
[GitHub] nifi issue #2866: NIFI-4710 Kerberos support for user auth in Docker instanc...
Github user SarthakSahu commented on the issue: https://github.com/apache/nifi/pull/2866 @apiri do you have any free time to review this. ---
[GitHub] nifi issue #2866: NIFI-4710 Kerberos support for user auth in Docker instanc...
Github user SarthakSahu commented on the issue: https://github.com/apache/nifi/pull/2866 Is anyone having bandwidth to review this. ---
[GitHub] nifi pull request #2866: NIFI-4710 Kerberos support for user auth in Docker ...
GitHub user SarthakSahu opened a pull request: https://github.com/apache/nifi/pull/2866 NIFI-4710 Kerberos support for user auth in Docker instances 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- where 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/SarthakSahu/nifi NIFI-4710 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/2866.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 #2866 commit 8904abd4ee319f5f0f0862795c1b266154216945 Author: Sahu Sarthak Date: 2018-07-09T13:06:55Z NIFI-4710 Kerberos support for user auth in Docker instances ---
