[
https://issues.apache.org/jira/browse/NIFI-10415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17598494#comment-17598494
]
Greg Biddy commented on NIFI-10415:
-----------------------------------
[~exceptionfactory] - It looks like we're squared away. For some reason, the
authentication workflow going directly from the Okta app to NiFi breaks the
login sequence but going directly to NiFi now redirects back to Okta which
appears to be working (not certain why as previously it resulted in the same
error and I didn't make any changes between then and now - our environment is
very complex... perhaps some Okta implementation had to propagate through our
environment).
As always, thanks for being so prompt in your responses. The help is much
appreciated.
> 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
> Attachments: auth_cookies.PNG
>
>
> 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)
