A technology firm is configuring single sign-on access to its AWS member accounts using an external SAML 2.0 Identity Provider (IdP). An administrator has successfully configured the external IdP and created a SAML provider entity in the target AWS account. However, when users try to log in, they receive an error stating that the federated role cannot be assumed. Which configuration is required in the target AWS account to resolve this issue?
- Configure the trust policy of the target IAM role to list the SAML provider's Amazon Resource Name (ARN) as the principal and specify the sts:AssumeRoleWithSAML action.Cevap
- BConfigure the trust policy of the target IAM role to use the external IdP's metadata URL as the principal and specify the standard sts:AssumeRole action.
- CAttach a Service Control Policy (SCP) to the target account's Organizational Unit (OU) that explicitly grants sts:AssumeRoleWithSAML access to the external identity provider.
- DConfigure the target IAM role's trust policy to trust the management account of the organization and use sts:AssumeRoleWithWebIdentity to federate the SAML users.
Cevap
Configure the trust policy of the target IAM role to list the SAML provider's Amazon Resource Name (ARN) as the principal and specify the sts:AssumeRoleWithSAML action.
The correct configuration is to define the trust relationship on the target IAM role to trust the SAML provider entity's Amazon Resource Name (ARN) in IAM, and to allow the sts:AssumeRoleWithSAML action. This allows the Security Token Service (STS) to validate the SAML assertion and issue temporary security credentials.
Adım Adım Çözüm
Anahtar Kavram
SAML 2.0 Identity Federation Trust Policies