You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can't set up a SAMLv2 IdP Initiated Identity Provider correctly because the issuer okta workforce provides isn't a URL.
Affects versions
1.27
Steps to reproduce
Create an SAMLv2 app in okta workforce
Follow the setup instructions here for sign on here (from the SSO page):
Configuring SAML 2.0 in your service provider
# to your service provider
# to your service provider as a user with Administrative rights.
Find the single sign on configuration section for your service provider, and enter the following information:
The Identity Provider Issuer is `IDkpalq1y2TYaG0oq5d6`. This might also be referred to as the Identity Provider Entity Id
The Identity Provider HTTP POST URL is https://example.okta.com/app/generic-saml/IDkpalq1y2TYaG0oq5d6/saml2. Okta currently supports the HTTP POST binding for SAML authentication.
You can download the Identity Provider Certificate by CLICKING HERE. You will need to import this into your service provider through their configuration UI.
Other setup: the ACS url is https://local.fusionauth.io/samlv2/acs/<idp initiated SAML v2 identity provider id>/<application id> and the service provider entity id is /samlv2/sp/<idp initiated SAML v2 identity provider id>. set Application username format to email.
Import the Okta certificate into keymaster (as a cert)
make sure you have a valid license.
Set up an IdP Initiated SAMLv2 Identity Provider: verification key is the public cert. user nameId for email. The issuer however, must be a URL. I used the post URL.
visit the 'embed link' url found on the 'general' tab in Okta.
If you look in the event logs, you'll see this message:
5/7/2021 01:46:10 AM GMT Assert the SAMLResponse with ID of [id1295232112418597119050170] has not already been processed.
5/7/2021 01:46:10 AM GMT Assert the [Audience] is eligible for confirmation if [NotBefore] is defined.
5/7/2021 01:46:10 AM GMT The [Audience] did define a [NotBefore] constraint and it is now available for assertion.
5/7/2021 01:46:10 AM GMT Assert the [Audience] is eligible for confirmation if [NotOnOrAfter] is defined.
5/7/2021 01:46:10 AM GMT The [Audience] did define a [NotOnOrAfter] constraint and it is still available for assertion.
5/7/2021 01:46:10 AM GMT Assert the [Audience] of the SAML response is equal to the expected value ending in [/samlv2/sp/REDACTED].
5/7/2021 01:46:10 AM GMT Assert the [Issuer] attribute is equal to the expected [https://example.okta.com/app/generic-saml/IDkpalq1y2TYaG0oq5d6/saml2].
5/7/2021 01:46:10 AM GMT Unable to verify the [Issuer]. Expected to find [https://example.okta.com/app/generic-saml/IDkpalq1y2TYaG0oq5d6/saml2] but found [IDkpalq1y2TYaG0oq5d6].
Expected behavior
The issuer is allowed to be set to the non URL value.
Additional context
Here's the full SAML response from the debug logs (somewhat redacted):
Closing, it looks like the doc for this new IdP is not out yet (as far as I could tell) so we'll just want to document that this field is a String and not a URL.
SAMLv2 IdP initiated Identity Provider doesn't accept Okta issuer
Description
You can't set up a SAMLv2 IdP Initiated Identity Provider correctly because the
issuer
okta workforce provides isn't a URL.Affects versions
1.27
Steps to reproduce
https://local.fusionauth.io/samlv2/acs/<idp initiated SAML v2 identity provider id>/<application id>
and the service provider entity id is/samlv2/sp/<idp initiated SAML v2 identity provider id>
. setApplication username format
to email.If you look in the event logs, you'll see this message:
Expected behavior
The
issuer
is allowed to be set to the non URL value.Additional context
Here's the full SAML response from the debug logs (somewhat redacted):
The text was updated successfully, but these errors were encountered: