Enforcing Email Verification with SAML

[christian.herzog]

I followed

Best Practice of Enforcing Email Verification

Problem Statement I am working on implementing email verification to prevent users from proceeding after registration and from signing in. Additionally, we aim to display a user-friendly message that explains the reason and provides instructions. What is considered the best practice in this scenario? Solution If you wish to enforce email verification before granting users access to your application, you can create a Post-Login Action (see the example below) that examines the email_verified prop…

and it works. Its SAML with Atlassian.
Only in case the email is not verified I get instead of Please verify your email before logging in. this error:

“{“key”:“badRequest”,“context”:{“message”:“Invalid customer saml login callback request”,“reason”:“does not contain at least one assertion within saml response”}}”
URL: id.atlassian.com/v2/customer/login/saml/callback?connection=saml…

SAML login fails with "Invalid issuer in the Assertion/Response" | Jira | Atlassian Documentation says to that error:
"After setting up SAML with Jira Data Center, the user is redirected to Jira but is not logged in. "

How can I configure this case in auth0?