AWS amazonq documentation change
Summary
Refined identity provider support statements to specify SAML 2.0 support for Microsoft Entra ID
Security assessment
Clarifies authentication method support without indicating resolution of security flaws. Improves documentation of security-related configuration options.
Diff
diff --git a/amazonq/latest/qbusiness-ug/create-application-iam.md b/amazonq/latest/qbusiness-ug/create-application-iam.md index 842851fe7..2d15e6bb9 100644 --- a//amazonq/latest/qbusiness-ug/create-application-iam.md +++ b//amazonq/latest/qbusiness-ug/create-application-iam.md @@ -11 +11 @@ Amazon Q Business supports identity federation through AWS Identity and Access M -You can use any third-party identity provider that supports Security Assertion Markup Language 2.0 (SAML 2.0) or OpenID Connect (OIDC) to provide an onboarding flow for your Amazon Q Business users. Such identity providers include, but aren't limited to Okta, Ping Identity, and Microsoft Entra ID. +You can use any third-party identity provider that supports Security Assertion Markup Language 2.0 (SAML 2.0) or OpenID Connect (OIDC) to provide an onboarding flow for your Amazon Q Business users. Such identity providers include, but aren't limited to Okta and Ping Identity. @@ -15 +15 @@ You can use any third-party identity provider that supports Security Assertion M -Amazon Q Business doesn't support OIDC for Google or Microsoft Entra ID. +Amazon Q Business supports Microsoft Entra ID with SAML 2.0, but doesn't support OIDC for Google or Microsoft Entra ID.