What is the role of the Meraki Dashboard as the service provider when using SAML for single sign-on to the Dashboard?

Question

Options

• AThe Dashboard generates the SAML request.
• BThe Dashboard provides user access credentials.
• CThe Dashboard parses the SAML request and authenticates users.
• DThe Dashboard generates the SAML response.

• A
  89% (41)
• B
  2% (1)
• C
  7% (3)
• D
  2% (1)

Explanation

In SAML SSO, the Service Provider (SP) is the application being accessed - here, the Meraki Dashboard. When a user attempts to log in, the SP's role is to initiate the flow by generating a SAML authentication request (AuthnRequest) and redirecting the user to the Identity Provider (IdP), making A correct.

Why the distractors are wrong:

• B - Providing credentials is never the SP's role; credentials belong to the user and are validated by the IdP.
• C - Authenticating users is the IdP's job (e.g., Okta, Azure AD). The SP trusts the IdP's verdict; it does not perform authentication itself.
• D - The IdP generates the SAML response (the signed assertion confirming identity) and sends it back to the SP. SP sends the request; IdP sends the response.

Memory tip: Think of SP = "Seeker" and IdP = "Decider." The SP seeks authentication by sending the request; the IdP decides and sends back the response. Meraki Dashboard is always the Seeker (SP).

No community discussion yet for this question.