[
https://issues.apache.org/jira/browse/NIFI-10313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17575898#comment-17575898
]
Malthe Borch commented on NIFI-10313:
-------------------------------------
[~exceptionfactory] I'm trying to find a reference on why sticky sessions would
be required, reading for example
[https://exceptionfactory.com/posts/2021/10/23/improving-jwt-authentication-in-apache-nifi/.|https://exceptionfactory.com/posts/2021/10/23/improving-jwt-authentication-in-apache-nifi/]
It does mention that the private key which signs the tokens is kept in memory
and perhaps specific to each node but it doesn't mention sticky/affinity
directly.
> 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)
