[
https://issues.apache.org/jira/browse/NIFI-10415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17598059#comment-17598059
]
David Handermann commented on NIFI-10415:
-----------------------------------------
You're welcome [~gregb].
Recent updates for NIFI-8648 added a new section to the NiFi documentation
regarding session affinity. The changes have been merged, but not yet released,
so here is a direct link, which might be helpful:
https://github.com/exceptionfactory/nifi/blob/2fc00e484b21871a3a644e6b07b68446f2d8aad5/nifi-docs/src/main/asciidoc/administration-guide.adoc#session-affinity
Feel free to follow up if you notice errors after enabling session affinity.
> SAML Login Sequence Fails
> -------------------------
>
> Key: NIFI-10415
> URL: https://issues.apache.org/jira/browse/NIFI-10415
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.16.3
> Environment: RHEL OS. Proxied Environment
> Reporter: Greg Biddy
> Priority: Major
> Labels: SAML
>
> Hello,
> I am attempting to configure a NiFi cluster to authenticate via Okta using
> SAML. I am in a proxied environment. When I navigate to NiFi via Okta, I
> receive the following error in the UI:
> Unable to continue login sequence
> The login request identifier was not found in the request. Unable to continue.
>
> I have configured the nifi.security.user.saml.idp.metadata.url property to
> reference a local file containing the metadata since Nifi cannot communicate
> with the IDP through the Proxy.
> Please verify if NiFi's SAML integration will work in a proxied environment.
>
> Thanks,
> Greg
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
