[
https://issues.apache.org/jira/browse/NIFI-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15064462#comment-15064462
]
Matt Gilman commented on NIFI-1309:
-----------------------------------
Found a couple minor issues around the account request being sent (specifically
with the Accept header). Also addressing on the REST API side as well.
Will address with an updated patch.
> Site-to-Site not automatically requesting an account
> ----------------------------------------------------
>
> Key: NIFI-1309
> URL: https://issues.apache.org/jira/browse/NIFI-1309
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Fix For: 0.4.1
>
> Attachments:
> 0001-NIFI-1309-Fixed-bug-where-two-slashes-were-getting-u.patch
>
>
> When a new Remote Process Group is added to the graph, if the system does not
> have an account on the remote instance, and site-to-site is secure, NiFi
> should automatically request a new account. This does not appear to be
> happening. Instead, we see log messages indicating that an attempt was made
> to the wrong URL:
> 2015-12-18 16:26:05,223 INFO [NiFi Web Server-58]
> o.a.n.w.a.config.NotFoundExceptionMapper
> com.sun.jersey.api.NotFoundException: null for uri:
> https://<hostname>:<port>/nifi-api//controller/users. Returning Not Found
> response.
> The /nifi-api//controller/users should be /nifi-api/controller/users
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
