[
https://issues.apache.org/jira/browse/NIFI-10313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17576005#comment-17576005
]
David Handermann commented on NIFI-10313:
-----------------------------------------
Although NiFi 1.17.0 included significant changes for SAML, the underlying
issue with the ingress controller routing to different nodes should still have
been a problem on 1.16.3 and earlier. There may still be something that changed
inadvertently in 1.17.0, but that is not yet clear.
As far as the cookies, {{__Secure-Request-Token}} is a UUID that the UI uses
for Cross Site Request Forgery mitigation, together with the custom
{{Request-Token}} HTTP header, which must match.
The {{__Secure-Authorization-Bearer}} cookie contains the JSON Web Token, used
for authenticating requests after initial login.
Both of these cookies should be present on requests from the NiFi UI.
> 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)
