Which Security Assertion Markup Language (SAML) configuration item is a pre-requisite to create a third party identity provider in Workspace ONE Access?

Question

Options

• ASAML AuthN Request
• BSAML AuthN Context
• CSAML Metadata
• DSAML Assertion

• B
  4% (1)
• C
  96% (25)

Explanation

SAML Metadata is the XML document that contains all the information needed to establish trust between Workspace ONE Access and a third-party identity provider - including the Entity ID, signing certificates, SSO endpoint URLs, and supported bindings. You must import the IdP's metadata first because Workspace ONE Access uses it to know where to send authentication requests and how to validate responses; without it, no trust relationship can be configured.

Why the distractors are wrong:

• A (AuthN Request): This is the XML message Workspace ONE Access dynamically generates and sends to the IdP during a login flow - it's an output of the configured integration, not a setup prerequisite.
• B (AuthN Context): This is an attribute within SAML messages that describes the authentication method used (e.g., password, smartcard) - a runtime parameter, not a configuration item required to define the IdP.
• D (SAML Assertion): This is the XML token the IdP sends back after authenticating the user - again, a runtime artifact produced during authentication, not something you configure beforehand.

Memory tip: Think of SAML Metadata as the IdP's "business card" - you must exchange cards (import metadata) before any authentication conversation (requests and assertions) can happen.

No community discussion yet for this question.