[
https://issues.apache.org/jira/browse/NIFI-10313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17575991#comment-17575991
]
David Handermann commented on NIFI-10313:
-----------------------------------------
If the {{ldap-provider}} configured in {{login-identity-providers.xml}}
specifies an expiration of 12 hours, then the NiFi session lifetime should be
12 hours. Based on that configuration, the {{clientIP.timeoutSeconds}} setting
for the Kubernetes ingress configuration should also be 12 hours, or 43200
seconds. With that configuration, the ingress controller should continue to
route requests to the same node for the duration of the NiFi session validity
window.
> 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)
