[
https://issues.apache.org/jira/browse/NIFI-10313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17575892#comment-17575892
]
David Handermann edited comment on NIFI-10313 at 8/5/22 3:02 PM:
-----------------------------------------------------------------
[~malthe] Those HTTP 400 and 409 responses are expected as part of the access
negotiation process. This looks like an opportunity to evaluate a better
approach in the UI, but the NiFi UI has followed this approach for a number of
versions, trying different types of authentication methods until one succeeds.
was (Author: exceptionfactory):
[~malthe] Those HTTP 400 and 409 responses are expected as part of the access
negotiation process. This looks like an opportunity to evaluate better approach
in the UI, but the NiFi UI has followed this approach for a number of versions,
trying different types of authentication methods until one succeeds.
> Unexpected "Access Token not found"
> -----------------------------------
>
> Key: NIFI-10313
> URL: https://issues.apache.org/jira/browse/NIFI-10313
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.17.0
> Reporter: Malthe Borch
> Assignee: David Handermann
> Priority: Major
> Attachments: NiFi-Errors.PNG, authorizers.xml, nifi.log
>
>
> I'm experiencing some unexpected "Access Token not found" errors after
> upgrading to 1.17.0.
> See attached traceback.
> What happens is that the NiFi UI seems to work but after a short while the
> view is redirected to a conflict page (Unable to communicate with NiFi).
> There are no other problems or evidence of the issue to be found in the logs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
