[
https://issues.apache.org/jira/browse/NIFI-10313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17574950#comment-17574950
]
David Handermann commented on NIFI-10313:
-----------------------------------------
[~malthe] Thanks for indicating that SAML is not configured.
Can you provide more details about your identity provider configuration? Are
you using LDAP for group resolution and Kerberos for authentication? OpenID
Connect excludes configuration with LDAP or Kerberos as a login identity
provider. It would be helpful if you can share some form of your
login-identity-providers.xml configuration.
With the Kubernetes deployment do you have anHTTP ingress configuration with
sticky sessions enabled?
> 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)
