[
https://issues.apache.org/jira/browse/NIFI-10313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17575248#comment-17575248
]
David Handermann commented on NIFI-10313:
-----------------------------------------
Thanks for providing the configuration details [~malthe]. The use of LDAP as
the groups provider makes sense based on the configuration.
It is important to note that sticky sessions are required when using any kind
of load balancer or proxy in front of the NiFi UI and REST API. Without sticky
sessions, the ingress controller could route requests to a different node,
which would be unable to verify the NiFi JSON Web Token, resulting in
authentication failures. Can you try enabling sticky sessions and see if that
improves the behavior?
> 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: 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)
