AWS agentworkspace documentation change
Summary
Updated branding from 'Amazon Connect Agent Workspace' to 'Amazon Connect Customer Agent Workspace' and maintained guidance on authentication best practices including third-party cookie deprecation prevention.
Security assessment
The changes are branding updates and minor wording adjustments. While authentication is security-related, there's no evidence of addressing a specific vulnerability. The third-party cookie discussion focuses on compatibility, not security flaws.
Diff
diff --git a/agentworkspace/latest/devguide/getting-started-authentication.md b/agentworkspace/latest/devguide/getting-started-authentication.md index 25e7f99ac..0a3629a15 100644 --- a//agentworkspace/latest/devguide/getting-started-authentication.md +++ b//agentworkspace/latest/devguide/getting-started-authentication.md @@ -5 +5 @@ -[Documentation](/index.html)[Amazon Connect Agent Workspace](/connect/index.html)[Developer guide](what-is-service.html) +[Documentation](/index.html)[Amazon Connect Customer Agent Workspace](/connect/index.html)[Developer Guide](what-is-service.html) @@ -7 +7 @@ -# Authentication for applications in Amazon Connect Agent Workspace +# Authentication for applications in Amazon Connect Customer agent workspace @@ -9 +9 @@ -Apps in the Amazon Connect agent workspace must provide their own authentication to their users. It is recommended that apps use the same identity provider that the Amazon Connect instance has been configured to use when it was created. This will make it so users only need to log in once for both the agent workspace and their applications, since they both use the same single sign on provider. +Apps in the Amazon Connect Customer agent workspace must provide their own authentication to their users. It is recommended that apps use the same identity provider that the Amazon Connect instance has been configured to use when it was created. This will make it so users only need to log in once for both the agent workspace and their applications, since they both use the same single sign on provider. @@ -13 +13 @@ Apps in the Amazon Connect agent workspace must provide their own authentication -On Jul 22, 2024, Google announced that they no longer plan to deprecate third-party cookies **[1]**. With this announcement, there will be no impact to third-party applications embedded within Amazon Connect’s agent workspace, unless third-party application users explicitly opt-in for deprecation. We advise third-party application developers to adopt the third-party cookie deprecation impact prevention solutions below as a forward-looking preventative measure. +On Jul 22, 2024, Google announced that they no longer plan to deprecate third-party cookies **[1]**. With this announcement, there will be no impact to third-party applications embedded within Amazon Connect Customer agent workspace, unless third-party application users explicitly opt-in for deprecation. We advise third-party application developers to adopt the third-party cookie deprecation impact prevention solutions below as a forward-looking preventative measure. @@ -25 +25 @@ For more information, see the [3P admin guide](https://docs.aws.amazon.com/conne -We are aware of the **Google Chrome** Third-Party Cookies Deprecation (3PCD) that may impact the third-party applications experience. If your application is embedded within the Amazon Connect’s agent workspace in an iframe and uses cookie based Authentication/Authorization, then your application is likely to be impacted by Third-Party Cookie Deprecation. You can test if your user experience will be impacted by 3PCD by using the following [Test for Breakage](https://developers.google.com/privacy-sandbox/3Pcd/prepare/test-for-breakage) guidance. +We are aware of the **Google Chrome** Third-Party Cookies Deprecation (3PCD) that may impact the third-party applications experience. If your application is embedded within the Amazon Connect Customer agent workspace in an iframe and uses cookie based Authentication/Authorization, then your application is likely to be impacted by Third-Party Cookie Deprecation. You can test if your user experience will be impacted by 3PCD by using the following [Test for Breakage](https://developers.google.com/privacy-sandbox/3Pcd/prepare/test-for-breakage) guidance. @@ -27 +27 @@ We are aware of the **Google Chrome** Third-Party Cookies Deprecation (3PCD) tha -Here are the recommendations to ensure customers continue to have good experiences when accessing your application within the Amazon Connect agent workspace with Google Chrome. +Here are the recommendations to ensure customers continue to have good experiences when accessing your application within the Amazon Connect Customer agent workspace with Google Chrome.