During a SAML authentication test across internally hosted apps, after a successful login to one partner app, subsequent apps open without explicit authentication requests. Which statement best explains this behavior?

• A. It is expected due to SAML authentication successfully logging on to all internal applications
• B. It is expected if all partners use a common SP
• C. It is expected if the Citrix ADC is the common IdP for all partners
• D. It indicates SAML authentication failed and the next protocol was used

Answer: (D)

This behavior shows how SAML single sign-on works across multiple apps that trust the same identity provider. After you log in to the first partner app, the identity provider creates a session for you. When you try to access other partner apps, those apps redirect you to the same IdP; since a session already exists, the IdP instantly issues the necessary SAML assertion to each app, letting you in without prompting for credentials again. This seamless access happens when all partners rely on a common IdP (for example, Citrix ADC acting as that IdP). If there isn’t a shared IdP, or if SAML had failed, you’d see re-authentication prompts or a fallback to another protocol, not silent access across apps.