CV0-002 · Question #289
A company is implementing a launchpad within an existing application that will point to an existing SaaS provider. One of the requirements is the user should not have to log on multiple times. SSO is
The correct answer is D. The federation is failing.. When Single Sign-On (SSO) is configured but users are still prompted for login credentials after being redirected to a SaaS provider, the most likely cause is an issue with the underlying federation mechanism.
Question
A company is implementing a launchpad within an existing application that will point to an existing SaaS provider. One of the requirements is the user should not have to log on multiple times. SSO is in place. When the launchpad is used, the user is redirected to SaaS providers as designed, but is asked for login credentials. Which of the following is the MOST likely cause of this issue?
Options
- AUsers do not exist within the SaaS provider.
- BGroup permissions are incorrect.
- CUsers do not exist in directory services.
- DThe federation is failing.
How the community answered
(27 responses)- A4% (1)
- B11% (3)
- C4% (1)
- D81% (22)
Why each option
When Single Sign-On (SSO) is configured but users are still prompted for login credentials after being redirected to a SaaS provider, the most likely cause is an issue with the underlying federation mechanism.
If users did not exist within the SaaS provider, the typical behavior would be an error indicating the user is unknown, rather than repeatedly prompting for login credentials after an SSO attempt.
Federation establishes the trust relationship and protocols (like SAML or OAuth) for SSO between an identity provider and a service provider (SaaS). If the federation is failing, the identity provider cannot properly assert the user's identity to the SaaS application, leading the SaaS to request re-authentication.
Concept tested: Troubleshooting SSO federation issues
Source: https://learn.microsoft.com/en-us/azure/active-directory/manage-apps/what-is-single-sign-on
Topics
Community Discussion
No community discussion yet for this question.