AWS sagemaker-unified-studio medium security documentation change
Summary
Added troubleshooting entry for 'Invalid or expired auth token' related to third-party cookies
Security assessment
Addresses authentication failures caused by browser security settings, directly impacting access control security. Provides guidance on managing security-related browser configurations.
Diff
diff --git a/sagemaker-unified-studio/latest/userguide/troubleshooting-issues.md b/sagemaker-unified-studio/latest/userguide/troubleshooting-issues.md index 23d638f37..d0f68aab6 100644 --- a//sagemaker-unified-studio/latest/userguide/troubleshooting-issues.md +++ b//sagemaker-unified-studio/latest/userguide/troubleshooting-issues.md @@ -5 +5 @@ -Troubleshooting AWS Lake Formation permissions for Amazon SageMaker Unified StudioAmazon EBS Volume Depletion with Local Notebook Execution Domain SAML Identity Provider Email Issue Project Creation Failure Data Explorer Visibility Issue Data Catalog Visibility Issue Connection to Amazon RDS MySQL in Existing VPC Visual ETL Flow Column Selection JupyterLab Configure Magic Error +Troubleshooting AWS Lake Formation permissions for Amazon SageMaker Unified StudioAmazon EBS Volume Depletion with Local Notebook Execution Domain SAML Identity Provider Email Issue Project Creation Failure Data Explorer Visibility Issue Data Catalog Visibility Issue Connection to Amazon RDS MySQL in Existing VPC Visual ETL Flow Column Selection Invalid or expired auth token when accessing an IDE JupyterLab Configure Magic Error @@ -151,0 +152,14 @@ When you start authoring a visual ETL flow, the data preview is also started. On +## Invalid or expired auth token when accessing an IDE + +**Question** + +When I tried to access an IDE in Amazon SageMaker Unified Studio I got an invalid or expired auth token error message. How do I resolve this? + +**Answer** + +This issue often occurs when third-party cookies are blocked. Amazon SageMaker Unified Studio uses the third-party cookies for authenticating into a Amazon SageMaker Unified Studio IDE since the IDE is hosted in a separate domain from the primary site. To help resolve this issue, ensure that third-party cookies are allowed in your browser. + +###### Note + +To do this in Safari, go to **Preferences** or **Settings** and ensure that on the **Privacy** page, the box next to **Prevent cross-site tracking** is unchecked. +