AWS Certified Solutions Architect - Professional free question 3 / 10 · Domain 2: Security, Compliance, and Governance
You connected your external IdP to IAM Identity Center with SAML 2.0. Sign-in works, but the IdP's users and groups do not appear on the screen for assigning access to AWS accounts. Which action is correct?
- Configure IAM Identity Center to query the directory of the IdP directly and import the users and groups from it
- SAML cannot query users and groups, so turn on automatic provisioning with SCIM and set the SCIM endpoint and token in the IdP
- Exchange the SAML metadata again; the metadata contains the list of users and groups, which are then synchronized
- Change the identity source of IAM Identity Center to AWS Managed Microsoft AD and copy the groups; register the users manually
Show the answer and explanation
Answer: B
Why this is correct
SAML has no way to query the IdP for users and groups. When you use an external IdP, you must provision users and groups into IAM Identity Center before you assign them to accounts or applications. You use either automatic provisioning with SCIM or manual provisioning. With SCIM, per the Provision users and groups with SCIM page (how-to-with-scim), you choose Enable on the Automatic provisioning information box in the IAM Identity Center settings, which displays the SCIM endpoint and access token, and you enter these values when you configure provisioning in your IdP.
Why the other options are wrong
"Exchange the SAML metadata again; the metadata contains the list of users and groups, which are then synchronized" … SAML metadata sets up the trust relationship; it does not carry a list of users and groups, so exchanging it again does not synchronize them.
"Configure IAM Identity Center to query the directory of the IdP directly and import the users and groups from it" … Because SAML has no way to query the IdP for users, there is no setting in which IAM Identity Center pulls them from the IdP.
"Change the identity source of IAM Identity Center to AWS Managed Microsoft AD and copy the groups; register the users manually" … AWS Managed Microsoft AD is a different identity source. It does not fit the premise of continuing to use the external IdP, and copying groups does not replace automatic synchronization.
Key point
SAML alone does not deliver users and groups; provision them with SCIM or manually. Per the SCIM page (how-to-with-scim), the SCIM endpoint and access token are displayed only once, when you enable automatic provisioning.