2V0-62.23 · Question #2
Refer to the exhibit. A user has attempted to launch an iOS application and during authentication they see this response. What is the cause of the issue?
The correct answer is C. You need to add the identifier to the Mobile SSO profile. Option C is correct because Mobile SSO profiles work by matching an app's bundle identifier - if that identifier isn't registered in the SSO profile, the authentication system doesn't recognize the app and cannot issue a token, regardless of whether the user or credentials are…
Question
Refer to the exhibit. A user has attempted to launch an iOS application and during authentication they see this response. What is the cause of the issue?
Options
- AThe user does not have access to that application
- BThey installed the application from the Apple App Store
- CYou need to add the identifier to the Mobile SSO profile
- DThe user put in the wrong email address
How the community answered
(19 responses)- A5% (1)
- B16% (3)
- C74% (14)
- D5% (1)
Explanation
Option C is correct because Mobile SSO profiles work by matching an app's bundle identifier - if that identifier isn't registered in the SSO profile, the authentication system doesn't recognize the app and cannot issue a token, regardless of whether the user or credentials are valid. The fix is simply adding the app's bundle ID to the Mobile SSO profile in your MDM solution (e.g., Okta, JAMF).
Why the distractors are wrong:
- A - An access/permission error would produce an authorization failure message, not an SSO configuration error; the user would still get past the authentication step.
- B - Distribution source (App Store vs. enterprise) is irrelevant to SSO profile configuration; the bundle identifier is the same either way.
- D - A wrong email would cause a credential or lookup failure, not an SSO profile mismatch.
Memory tip: Think of the Mobile SSO profile as a guest list - the app's identifier must be on the list before SSO will let it in. Missing from the list = no entry, no matter who you are.
Topics
Community Discussion
No community discussion yet for this question.