<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D5WR00001H61Ko0AJOkta Classic EngineMulti-Factor AuthenticationAnswered2026-11-03T22:11:22.000Z2026-02-10T01:37:16.000Z2026-11-03T22:11:22.000Z

SilvanoS.83351 (Customer) asked a question.

App Sign-In password-only reauth not honored for SP-initiated SAML in pop-up (Global Session re-triggers MFA)

We’re integrating Okta (OIE) with Veeva Vault eSignature using SP-initiated SAML. We have two app sign-in policies:

 

  • Primary app: Password + MFA
  • eSignature (secondary/hidden app): Password-only, re-auth every time

 

Global Session Policy requires MFA (standard workforce baseline). The org setting “Require possession factor before password during MFA” is disabled.

 

During eSignature, Veeva launches the IdP flow in a browser pop-up. Even when a valid Okta session exists in the main window, Okta often treats the pop-up as a new session and re-applies Global Session MFA before the app sign-in policy is evaluated.

 

Question:

Is this expected behavior due to Okta session cookies not being reliably reused in pop-ups? And is there any supported way (custom domain, redirect mode, etc.) to ensure session reuse so that the app sign-in password-only reauth can be honored?

 


This question is closed.
Loading
App Sign-In password-only reauth not honored for SP-initiated SAML in pop-up (Global Session re-triggers MFA)
Okta Support Agent (Beta)

Terms of Service

Hello! I'm the Okta Support Agent (Beta), your go-to resource for questions about Okta products. Please remember for your security and privacy, do not share any Personally Identifiable Information (PII) such as passwords, IP addresses, or other details with me.

Okta Privacy Policy and Terms of Service apply