AWS connect documentation change
Summary
Updated terminology from 'Amazon Connect' to 'Connect Customer' throughout the document
Security assessment
Changes are purely terminological (branding update) without modifying security configurations, authentication flows, or permissions. The SSO functionality remains identical.
Diff
diff --git a/connect/latest/adminguide/3p-apps-sso.md b/connect/latest/adminguide/3p-apps-sso.md index d4b2fd865..cb40dddc3 100644 --- a//connect/latest/adminguide/3p-apps-sso.md +++ b//connect/latest/adminguide/3p-apps-sso.md @@ -7 +7 @@ -# Set up SSO Federation for third-party apps in your Amazon Connect instance +# Set up SSO Federation for third-party apps in your Connect Customer instance @@ -9 +9 @@ -A user can use Single-Sign-On to federate into multiple third-party applications that have been setup within their Amazon Connect instance without the need to authenticate separately for each application. +A user can use Single-Sign-On to federate into multiple third-party applications that have been setup within their Connect Customer instance without the need to authenticate separately for each application. @@ -15 +15 @@ Your third-party (3P) application can seamlessly complete the Sign-On flow withi -###### Setup SSO for third-party apps that exist within your Amazon Connect instances +###### Setup SSO for third-party apps that exist within your Connect Customer instances @@ -21 +21 @@ Your third-party (3P) application can seamlessly complete the Sign-On flow withi - 3. Set up an Amazon Connect instance and [Configure SAML with IAM for Amazon Connect](./configure-saml.html). + 3. Set up an Connect Customer instance and [Configure SAML with IAM for Connect Customer](./configure-saml.html). @@ -23 +23 @@ Your third-party (3P) application can seamlessly complete the Sign-On flow withi - 4. Set up other applications within your Identity Provider which you will be integrating with your Amazon Connect instance. + 4. Set up other applications within your Identity Provider which you will be integrating with your Connect Customer instance. @@ -25 +25 @@ Your third-party (3P) application can seamlessly complete the Sign-On flow withi - 5. Attach each individual user identity to any applications within the Identity Provider that will be integrated with your Amazon Connect instance. You can control which agent has access to an application on the Amazon Connect agent workspace by providing more granular application specific permissions in security profiles. For more information, see [Security profile permissions for using third-party applications in Amazon Connect](./assign-security-profile-3p-apps.html). + 5. Attach each individual user identity to any applications within the Identity Provider that will be integrated with your Connect Customer instance. You can control which agent has access to an application on the Connect Customer agent workspace by providing more granular application specific permissions in security profiles. For more information, see [Security profile permissions for using third-party applications in Connect Customer](./assign-security-profile-3p-apps.html). @@ -27 +27 @@ Your third-party (3P) application can seamlessly complete the Sign-On flow withi - 6. After a user has signed into their Identity Provider, they can federate into their Amazon Connect instance which has third-party applications configured and they can federate into each application (if the application has been setup for SSO) without the need of their username and password. + 6. After a user has signed into their Identity Provider, they can federate into their Connect Customer instance which has third-party applications configured and they can federate into each application (if the application has been setup for SSO) without the need of their username and password.