AWS singlesignon: Updated external IdP setup reference
Summary
Added specificity to external IdP setup steps in PingFederate documentation
Security assessment
Ensures accurate references to external IdP configuration steps, reducing deployment errors
Evidence
- * If you replicated IAM Identity Center to additional Regions, you must update your identity provider configuration to enable access to AWS managed applications and AWS accounts from those Regions. For more details, see [Step 3: Update external IdP setup](./replicate-to-additional-region.html#update-external-idp-setup).
Diff
diff --git a/singlesignon/latest/userguide/pingfederate-idp.md b/singlesignon/latest/userguide/pingfederate-idp.md index 9466bfd74..5583d54cc 100644 --- a//singlesignon/latest/userguide/pingfederate-idp.md +++ b//singlesignon/latest/userguide/pingfederate-idp.md @@ -54 +54 @@ You'll need the following before you can get started: - * If you replicated IAM Identity Center to additional Regions, you must update your identity provider configuration to enable access to AWS managed applications and AWS accounts from those Regions. For more details, see [Step 3: Update external IdP setup](./replicate-to-additional-region.html#update-external-idp-setup). See the PingFederate documentation for additional details. + * If you replicated IAM Identity Center to additional Regions, you must update your identity provider configuration to enable access to AWS managed applications and AWS accounts from those Regions. For more details, see [Step 3 (external identity providers only): Update external IdP setup](./replicate-to-additional-region.html#update-external-idp-setup). See the PingFederate documentation for additional details.