[
https://issues.apache.org/jira/browse/NIFI-10313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17575899#comment-17575899
]
David Handermann commented on NIFI-10313:
-----------------------------------------
Thanks for noting the ssl-passthrough configuration. Unfortunately session
affinity is a requirement for access a NiFi cluster nodes through a load
balancer. Each NiFi node signs and verifies JSON Web Tokens during request
authentication, so a JWT from one node will not be accepted on another node.
This could be changed, but other cluster operations involve two-phase commits
where a subsequent request must be processed by the same node that received the
initial request. Without some way to guarantee access to the same node,
requests will be subject to intermittent failure when a load balancer directs
requests to a different node in the course of a single authenticated session.
> 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)
