nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ijokarumawak <...@git.apache.org>
Subject [GitHub] nifi pull request #497: NIFI-1857: HTTPS Site-to-Site
Date Tue, 07 Jun 2016 13:41:37 GMT
Github user ijokarumawak commented on a diff in the pull request:

    https://github.com/apache/nifi/pull/497#discussion_r66071968
  
    --- Diff: nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/remote/StandardRemoteProcessGroup.java
---
    @@ -1117,31 +1164,39 @@ public void run() {
                         final String remoteInstanceId = dto.getInstanceId();
                         final boolean isPointingToCluster = flowController.getInstanceId().equals(remoteInstanceId);
                         pointsToCluster.set(isPointingToCluster);
    -                } else if (statusCode == UNAUTHORIZED_STATUS_CODE) {
    -                    try {
    -                        final ClientResponse requestAccountResponse = utils.issueRegistrationRequest(apiUri.toString());
    --- End diff --
    
    Hi @mcgilman @markap14 
    RPG used to create a NiFi user automatically by sending a request to `/controller/users`
which UserResource listens to. But that resource has been removed by #359 and it's not listed
on [Support Authorizer API](https://cwiki.apache.org/confluence/display/NIFI/Support+Authorizer+API)
resource list.
    Does that mean we no longer have to create an user automatically?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message