AWS bedrock: Add Salesforce to real-time ACL verification support
Summary
Adds Salesforce to the list of connectors supporting real-time ACL verification, adds a table row documenting that Salesforce uses the OAuth 2.0 JWT Bearer Flow to check access as the querying user (requires OAUTH2_WITH_JWT_BEARER auth type, Experience Cloud users unsupported), and links to the new Salesforce ACL page.
Security assessment
The added line documents that Salesforce ACL-aware retrieval performs a real-time per-user access check via OAuth 2.0 JWT Bearer Flow, which is authorization/permission-enforcement documentation (preventing users from retrieving documents they cannot access). It documents an existing security capability rather than fixing a specific vulnerability, so it is security documentation, not an incident/CVE response.
Evidence
+[Salesforce](./kb-managed-ds-salesforce-acl.html) | Supported | Supported | Uses the OAuth 2.0 JWT Bearer Flow to check access as the querying user. Requires `OAUTH2_WITH_JWT_BEARER` auth type. Experience Cloud users are not supported.
Diff
diff --git a/bedrock/latest/userguide/kb-managed-acl.md b/bedrock/latest/userguide/kb-managed-acl.md index 606bd9e..107661b 100644 --- a//bedrock/latest/userguide/kb-managed-acl.md +++ b//bedrock/latest/userguide/kb-managed-acl.md @@ -23 +23 @@ ACL-aware retrieval operates in two stages: - * **Real-time ACL verification** — For connectors that support it (SharePoint, OneDrive, Google Drive, Confluence, Confluence Data Center, Box, and Zendesk), Bedrock Managed Knowledge Base makes a real-time call to the data source to verify that the user still has access to each returned document. This catches permission changes that occurred between syncs. For ServiceNow, real-time verification applies only to advanced (scripted) user criteria and requires the real-time ACL verifier endpoint that you install in your ServiceNow instance; all other user criteria are resolved at crawl time and permission changes take effect only after the next sync. S3 and Custom connectors do not support real-time verification because their ACL metadata is provided by the customer through configuration files rather than crawled from a live permission system. + * **Real-time ACL verification** — For connectors that support it (SharePoint, OneDrive, Google Drive, Confluence, Confluence Data Center, Box, Zendesk, and Salesforce), Bedrock Managed Knowledge Base makes a real-time call to the data source to verify that the user still has access to each returned document. This catches permission changes that occurred between syncs. For ServiceNow, real-time verification applies only to advanced (scripted) user criteria and requires the real-time ACL verifier endpoint that you install in your ServiceNow instance; all other user criteria are resolved at crawl time and permission changes take effect only after the next sync. S3 and Custom connectors do not support real-time verification because their ACL metadata is provided by the customer through configuration files rather than crawled from a live permission system. @@ -57,0 +58 @@ ACL support by connector Connector | Pre-retrieval filter | Real-time ACL | Note +[Salesforce](./kb-managed-ds-salesforce-acl.html) | Supported | Supported | Uses the OAuth 2.0 JWT Bearer Flow to check access as the querying user. Requires `OAUTH2_WITH_JWT_BEARER` auth type. Experience Cloud users are not supported. @@ -79,0 +81,2 @@ For connector-specific ACL configuration details, see: + * [ACL awareness for Salesforce](./kb-managed-ds-salesforce-acl.html) +