[
https://issues.apache.org/jira/browse/NIFI-10313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17574935#comment-17574935
]
David Handermann commented on NIFI-10313:
-----------------------------------------
Thanks for reporting this issue [~malthe].
The {{Access Token not found}} message and the associated stack trace indicate
that the web browser is not providing the JWT through the standard secure
cookie. In normal operation, the browser sends the JWT in a cookie named
{{__Secure-Authorization-Bearer}}, then this method reads the token and
extracts the expiration. NiFi uses session-based expiration for this cookie,
meaning that it should remain available until the browser is closed.
If the NiFi UI works for a short period of time, and then redirects to an error
page, one possibility is that the JWT has a short expiration. Can you provide
the value configured for {{nifi.security.user.saml.authentication.expiration}}
from {{nifi.properties}}? The default value is 12 hours.
It would also be helpful if you can provide some additional details about the
environment, including the SAML Identity Provider used, and whether NiFi is
running behind some kind of proxy or load balancer.
The {{nifi-request.log}} tracks HTTP requests and responses to the NiFi web
server, so it may also have some useful troubleshooting information for
requests leading up to this particular error.
> 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.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)
