Skip to content

Python: Clarify identifier security guidance#6510

Open
chetantoshniwal wants to merge 1 commit into
mainfrom
sreagent/docs-identifier-guidance-20260614
Open

Python: Clarify identifier security guidance#6510
chetantoshniwal wants to merge 1 commit into
mainfrom
sreagent/docs-identifier-guidance-20260614

Conversation

@chetantoshniwal

Copy link
Copy Markdown
Contributor

Summary

  • clarify that AG-UI conversation identifiers provide continuity, not authorization
  • document that A2A hosts must bind client-supplied identifiers to authenticated access boundaries
  • document that Azure Functions HITL status/respond endpoints require authz and that workflow IDs are correlation handles only

Validation

  • git diff --check

Created by Azure SRE Agent: Open thread on Saw | Open thread on MSFT

Co-authored-by: Azure SRE Agent <noreply@microsoft.com>
Copilot AI review requested due to automatic review settings June 14, 2026 06:27
@moonbox3 moonbox3 added documentation Improvements or additions to documentation python .NET labels Jun 14, 2026
@github-actions github-actions Bot changed the title [Generated by SRE Agent] Clarify identifier security guidance .NET: [Generated by SRE Agent] Clarify identifier security guidance Jun 14, 2026
@github-actions github-actions Bot changed the title .NET: [Generated by SRE Agent] Clarify identifier security guidance Python: [Generated by SRE Agent] Clarify identifier security guidance Jun 14, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Clarifies security guidance across Agent Framework samples/docs to emphasize that client-supplied identifiers provide correlation/continuity, not authorization, and that hosts must enforce authentication/authorization at real access boundaries.

Changes:

  • Azure Functions HITL sample: documents that workflow status/respond endpoints must be protected by authn/authz and that instanceId/requestId are correlation handles only.
  • Python A2A package README: adds security considerations for production hosts, warning against treating task/thread/session identifiers as bearer credentials.
  • .NET AG-UI sample README: clarifies ConversationId is for continuity only and points to session isolation (UseClaimsBasedSessionIsolation(...)) for multi-user storage separation.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File Description
python/samples/04-hosting/azure_functions/12_workflow_hitl/README.md Adds guidance to protect HITL status/respond endpoints and treat IDs as non-secret correlation handles.
python/packages/a2a/README.md Adds security considerations for A2A hosting, emphasizing authn/authz and safe binding of client identifiers.
dotnet/samples/02-agents/AGUI/README.md Adds AG-UI identifier security guidance and suggests claims-based session isolation for multi-user hosts.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automated Code Review

Reviewers: 5 | Confidence: 86% | Result: All clear

Reviewed: Correctness, Security Reliability, Test Coverage, Failure Modes, Design Approach


Automated review by chetantoshniwal's agents

@github-actions

Copy link
Copy Markdown
Contributor

Python Test Coverage

Python Test Coverage Report •
FileStmtsMissCoverMissing
TOTAL39720450388% 
report-only-changed-files is enabled. No files were changed during this commit :)

Python Unit Test Overview

Tests Skipped Failures Errors Time
7947 34 💤 0 ❌ 0 🔥 2m 4s ⏱️

@chetantoshniwal chetantoshniwal changed the title Python: [Generated by SRE Agent] Clarify identifier security guidance Python: Clarify identifier security guidance Jun 14, 2026
@chetantoshniwal chetantoshniwal requested a review from moonbox3 June 14, 2026 07:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation .NET python

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants