[
https://issues.apache.org/jira/browse/NIFI-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15318479#comment-15318479
]
ASF GitHub Bot commented on NIFI-1857:
--------------------------------------
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?
> Support HTTP(S) as a transport mechanism for Site-to-Site
> ---------------------------------------------------------
>
> Key: NIFI-1857
> URL: https://issues.apache.org/jira/browse/NIFI-1857
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Koji Kawamura
> Assignee: Koji Kawamura
> Original Estimate: 480h
> Remaining Estimate: 480h
>
> We should add support for using HTTP(S) for site-to-site to be an alternative
> to the current socket based approach.
> This would support the same push based or pull based approach site-to-site
> offers now but it would use HTTP(S) for all interactions to include learning
> about ports, learning about NCM topology, and actually exchanging data. This
> mechanism should also support interaction via an HTTP proxy.
> This would also require some UI work to allow the user to specify which
> protocol for site-to-site to use such as 'raw' vs 'http'. We also need to
> document any limitations with regard to SSL support for this mode and we'd
> need to provide 'how-to' when using proxies like http_proxy or something else.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
