[
https://issues.apache.org/jira/browse/NIFI-10415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17598381#comment-17598381
]
Greg Biddy commented on NIFI-10415:
-----------------------------------
[~exceptionfactory] - One question regarding session affinity: While we are
running a NiFi cluster, it isn't deployed behind a load balancer. So Okta has
been configured to send all authentication requests to only one node of the
cluster, which is always the same node. This being the case, is setting session
affinity on the proxy server still relevant?
Thanks again.
> 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
> Assignee: David Handermann
> 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)
