aws-govcloudvendorNewsThe Broadside1 min read

AWS adds ForceAuthn support to IAM Identity Center

The useful part is narrower than the announcement sounds: expired portal sessions can require a fresh IdP check.


TL;DR

AWS IAM Identity Center now supports ForceAuthn in SAML requests and adds a Required re-authentication setting for workforce users after their interactive session expires. The setting covers IAM Identity Center instances using an external identity provider, only for service provider initiated sign-ins through the AWS access portal. CloudTrail logs setting changes. For regulated workloads, this closes a session-renewal gap, but it isn't a universal AWS access-control switch.

AWS has added a real compliance knob to IAM Identity Center, and it’s worth reading the edges before anyone turns it into a slide that says “mandatory re-authentication solved.” The new option lets administrators require workforce users to re-authenticate with an external identity provider when their IAM Identity Center user interactive session expires, instead of letting IAM Identity Center renew the session through the user’s existing IdP session.

Mechanically, IAM Identity Center does this by adding the SAML 2.0 ForceAuthn attribute to the SAML request sent to the external IdP. AWS says the setting is available for organization or account instances connected to an external IdP, at no additional cost, in every Region where IAM Identity Center is available. Changes to the setting are logged in AWS CloudTrail, which matters because the control itself will become evidence for someone’s audit file.

The limitation is operational, not cosmetic. AWS says the setting applies only to service provider initiated sign-ins, where the user starts through the AWS access portal URL. AWS’s IAM Identity Center documentation also says the IdP must honor ForceAuthn for users to actually be prompted, and that the behavior applies only to sign-ins that start from the AWS access portal (https://docs.aws.amazon.com/singlesignon/latest/userguide/other-idps.html).

So the Monday work is straightforward: confirm which IAM Identity Center instances use an external IdP, decide whether expired sessions must force explicit user verification for the regulated workload, test whether the IdP actually honors ForceAuthn, and preserve the CloudTrail record for the change. The feature helps with strict re-authentication policies. It doesn’t eliminate the need to understand the sign-in path.


Published ·Deep Fathom