[jira] [Comment Edited] (NIFI-10313) Unexpected "Access Token not found"

["Malthe Borch (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-10313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17574942#comment-17574942 ] 

Malthe Borch edited comment on NIFI-10313 at 8/3/22 9:58 PM:
-------------------------------------------------------------

We're actually not using SAML at all and do not have a setting for {{{}nifi.security.user.saml.authentication.expiration{}}}.

We use LDAP and Kerberos, configured in {{{}login-identity-providers.xml{}}}.

Looking through {{nifi-request.log}} it doesn't seem to have any useful information on this.


was (Author: malthe):
We're actually not using SAML at all and do not have a setting for {{{{{}nifi.security.user.saml.authentication.expiration{}}}.}}

We use LDAP and Kerberos, configured in {{{}login-identity-providers.xml{}}}.

Looking through {{nifi-request.log}} it doesn't seem to have any useful information on this.

> 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)