Refer to the exhibit. The Workspace ONE Administrator has received complaints from end users that they are unable to access web applications from the Workspace ONE Access catalog. The exhibit…

Question

Exhibit

Options

• ASAML Certificate
• BSAML Sign-On URL
• CSAML Entity ID
• DSAML Recipient

• A
  5% (2)
• B
  16% (7)
• C
  75% (33)
• D
  5% (2)

Explanation

SAML Entity ID is the unique identifier that links the Identity Provider (Workspace ONE Access) to the Service Provider (the web application). When the Entity ID configured in Workspace ONE Access doesn't exactly match what the web application expects, the SAML assertion is rejected and users are blocked from the catalog - the most likely cause of the error shown in the exhibit.

Why the distractors are wrong:

• A. SAML Certificate - A certificate problem produces signature validation errors or "untrusted certificate" messages, not a general catalog access failure.
• B. SAML Sign-On URL - An incorrect Sign-On URL would prevent the SAML request from being sent at all (redirect or 404 error), rather than failing at the application level.
• D. SAML Recipient - The Recipient field restricts where an assertion can be consumed; mismatches here are less common and typically affect post-authentication delivery, not catalog access initiation.

Memory tip: Think of the Entity ID as the application's "social security number" - both sides of the SAML handshake must agree on the exact value, including capitalization and trailing slashes. Any mismatch = no trust = no access.

No community discussion yet for this question.