AWS connect documentation change
Summary
Renamed 'Amazon Connect' to 'Connect Customer' throughout the document including headings, descriptions, error messages, and troubleshooting steps.
Security assessment
Changes are purely branding/naming updates without any modifications to security configurations, authentication protocols, or vulnerability descriptions. The SAML troubleshooting process remains technically identical.
Diff
diff --git a/connect/latest/adminguide/troubleshoot-saml.md b/connect/latest/adminguide/troubleshoot-saml.md index ea99ccf5f..c901e9065 100644 --- a//connect/latest/adminguide/troubleshoot-saml.md +++ b//connect/latest/adminguide/troubleshoot-saml.md @@ -9 +9 @@ Error Message: Access Denied. Your account has been authenticated, but has not b -# Troubleshoot SAML with Amazon Connect +# Troubleshoot SAML with Connect Customer @@ -11 +11 @@ Error Message: Access Denied. Your account has been authenticated, but has not b -This article explains how to troubleshoot and resolve some of the most common issues customers encounter when using SAML with Amazon Connect. +This article explains how to troubleshoot and resolve some of the most common issues customers encounter when using SAML with Connect Customer. @@ -13 +13 @@ This article explains how to troubleshoot and resolve some of the most common is -If you're troubleshooting your integration with other identity providers such as Okta, PingIdentify, Azure AD, and more, see [Amazon Connect SSO Setup Workshop](https://catalog.workshops.aws/workshops/33e6d0e7-f927-4531-abb1-f28a86ba0872/en-US). +If you're troubleshooting your integration with other identity providers such as Okta, PingIdentify, Azure AD, and more, see [Connect Customer SSO Setup Workshop](https://catalog.workshops.aws/workshops/33e6d0e7-f927-4531-abb1-f28a86ba0872/en-US). @@ -21 +21 @@ If you're troubleshooting your integration with other identity providers such as -This error means that the user has successfully authenticated using SAML into the AWS SAML login endpoint. However, the user could not be matched/found inside Amazon Connect. This usually indicates one of the following: +This error means that the user has successfully authenticated using SAML into the AWS SAML login endpoint. However, the user could not be matched/found inside Connect Customer. This usually indicates one of the following: @@ -23 +23 @@ This error means that the user has successfully authenticated using SAML into th - * The username in Amazon Connect doesn't match the `RoleSessionName` SAML attribute specified in the SAML response returned by the identity provider. + * The username in Connect Customer doesn't match the `RoleSessionName` SAML attribute specified in the SAML response returned by the identity provider. @@ -25 +25 @@ This error means that the user has successfully authenticated using SAML into th - * The user doesn't exist in Amazon Connect. + * The user doesn't exist in Connect Customer. @@ -34 +34 @@ This error means that the user has successfully authenticated using SAML into th -Use the following steps to check the RoleSessionName SAML attribute specified in the SAML response returned by the identity provider, and then retrieve and compare with the login name in Amazon Connect. +Use the following steps to check the RoleSessionName SAML attribute specified in the SAML response returned by the identity provider, and then retrieve and compare with the login name in Connect Customer. @@ -58 +58 @@ This script uses a simple python command to decode the SAMLResponse from its ori - 5. Check whether the username returned in from the previous step exists as a user in your Amazon Connect instance: + 5. Check whether the username returned in from the previous step exists as a user in your Connect Customer instance: @@ -62 +62 @@ $ aws connect list-users --instance-id [INSTANCE_ID] | grep $username - * If the final grep does not return a result then this means that the user does not exist in your Amazon Connect instance or it has been created with a different case/capitalization. + * If the final grep does not return a result then this means that the user does not exist in your Connect Customer instance or it has been created with a different case/capitalization. @@ -64 +64 @@ $ aws connect list-users --instance-id [INSTANCE_ID] | grep $username - * If your Amazon Connect instance has many users, the response from the ListUsers API call maybe paginated. Use the `NextToken` returned by the API to fetch the rest of the users. For more information, see [ListUsers](https://docs.aws.amazon.com/connect/latest/APIReference/API_ListUsers.html). + * If your Connect Customer instance has many users, the response from the ListUsers API call maybe paginated. Use the `NextToken` returned by the API to fetch the rest of the users. For more information, see [ListUsers](https://docs.aws.amazon.com/connect/latest/APIReference/API_ListUsers.html). @@ -81 +81 @@ Following is an image from a sample SAML Response. In this case, the identity pr -The role that the user has assumed has successfully authenticated using SAML. However, the role doesn't have permission to call the GetFederationToken API for Amazon Connect. This call is required so the user can log in to your Amazon Connect instance using SAML. +The role that the user has assumed has successfully authenticated using SAML. However, the role doesn't have permission to call the GetFederationToken API for Connect Customer. This call is required so the user can log in to your Connect Customer instance using SAML. @@ -117 +117 @@ JSON -If you see the **Session expired** message while logging in, you probably just need to refresh the session token. Go to your identity provider and log in. Refresh the Amazon Connect page. If you still get this message, contact your IT team. +If you see the **Session expired** message while logging in, you probably just need to refresh the session token. Go to your identity provider and log in. Refresh the Connect Customer page. If you still get this message, contact your IT team. @@ -125 +125 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Configure SAML with IAM for Amazon Connect +Configure SAML with IAM for Connect Customer