[
https://issues.apache.org/jira/browse/NIFI-10415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17598445#comment-17598445
]
Greg Biddy commented on NIFI-10415:
-----------------------------------
[~exceptionfactory] - I receive this error every time I attempt to authenticate
using Okta and all authentication is done through nifi-1. I can successfully
authenticate however if I don't go through Okta but navigate directly to nifi-1
(or any other node for that matter) using client certificate authentication.
I should note that even when I go through Okta, the browser is prompting for
which client certificate to use. The error page occurs regardless of whether I
select the certificate or cancel out of the dialog box.
> 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)
