AWS appstream2 documentation change
Summary
Replaced 'AppStream 2.0' with 'WorkSpaces Applications' in SAML authentication flow documentation
Security assessment
Documentation updates for service name consistency. The authentication mechanism and security implications remain identical, only terminology changes.
Diff
diff --git a/appstream2/latest/developerguide/external-identity-providers-example.md b/appstream2/latest/developerguide/external-identity-providers-example.md index 4d6540cf4..caff04f54 100644 --- a//appstream2/latest/developerguide/external-identity-providers-example.md +++ b//appstream2/latest/developerguide/external-identity-providers-example.md @@ -3 +3 @@ -[Documentation](/index.html)[Amazon AppStream 2.0](/appstream2/index.html)[Administration Guide](what-is-appstream.html) +[Documentation](/index.html)[Amazon WorkSpaces Applications](/appstream2/index.html)[Administration Guide](what-is-appstream.html) @@ -7 +7 @@ -The following diagram illustrates the authentication flow between AppStream 2.0 and a third-party identity provider (IdP). In this example, the administrator has set up a sign-in page to access AppStream 2.0, called `applications.exampleco.com`. The webpage uses a SAML 2.0–compliant federation service to trigger a sign-on request. The administrator has also set up a user to allow access to AppStream 2.0. +The following diagram illustrates the authentication flow between WorkSpaces Applications and a third-party identity provider (IdP). In this example, the administrator has set up a sign-in page to access WorkSpaces Applications, called `applications.exampleco.com`. The webpage uses a SAML 2.0–compliant federation service to trigger a sign-on request. The administrator has also set up a user to allow access to WorkSpaces Applications. @@ -9 +9 @@ The following diagram illustrates the authentication flow between AppStream 2.0 - + @@ -19 +19 @@ The following diagram illustrates the authentication flow between AppStream 2.0 - 5. The user's browser posts the SAML assertion to the AWS Sign-In SAML endpoint (`https://signin.aws.amazon.com/saml`). AWS Sign-In receives the SAML request, processes the request, authenticates the user, and forwards the authentication token to AppStream 2.0. + 5. The user's browser posts the SAML assertion to the AWS Sign-In SAML endpoint (`https://signin.aws.amazon.com/saml`). AWS Sign-In receives the SAML request, processes the request, authenticates the user, and forwards the authentication token to WorkSpaces Applications. @@ -23 +23 @@ For information about working with SAML in the AWS GovCloud (US) Regions, see [A - 6. Using the authentication token from AWS, AppStream 2.0 authorizes the user and presents applications to the browser. + 6. Using the authentication token from AWS, WorkSpaces Applications authorizes the user and presents applications to the browser. @@ -28 +28 @@ For information about working with SAML in the AWS GovCloud (US) Regions, see [A -From the user's perspective, this process happens transparently. The user starts at your organization's internal portal and is automatically redirected to an AppStream 2.0 application portal without being required to enter AWS credentials. +From the user's perspective, this process happens transparently. The user starts at your organization's internal portal and is automatically redirected to an WorkSpaces Applications application portal without being required to enter AWS credentials.