[Design] Support External Evaluation Policy (Invoke) in management SDKs

未关闭
  • 哪里不对？
#50,818 0 条评论 2 个 reaction 已指派 2 人 在 GitHub 查看

维护者通常 1 天内回复

@weidongxu-microsoft 已经在做这个了。

开始于 2026年10月15日。

  • #50819 来自 @copilot-swe-agent —— 已关闭，未合并

评估

这个 Issue 还没有评估数据。

描述

Summary

Design support for Azure Policy External Evaluation ("Invoke") in Java management SDKs.

The SDK should handle the following flow:

  1. Detect 403 RequestDisallowedByPolicy with missingPolicyTokenDetails.
  2. Call acquirePolicyToken using the original request URI, method, and payload.
  3. Add the returned token to x-ms-policy-external-evaluations.
  4. Replay the original operation once.

Cross-language context and service clarifications are tracked in:
https://github.com/Azure/azure-sdk/issues/10081

An initial Java prototype is available at:
https://github.com/Azure/azure-sdk-for-java/pull/49701

Byte-for-byte payload requirement

For an operation with request-body byte sequence B, the following must use the same serialized bytes:

  1. The original ARM operation body.
  2. acquirePolicyToken.operation.content.
  3. The replayed ARM operation body.

Logical JSON equality is insufficient. Deserializing and reserializing the payload may change property ordering, whitespace, escaping, number formatting, null handling, or encoding and invalidate the token's content binding.

The implementation should retain the final serialized request content and reuse it without modification for token acquisition and replay. Bodyless operations such as DELETE should preserve the service-defined empty/null content behavior.

Design goals

  • Work across management libraries without service-specific changes.
  • Support PUT, PATCH, POST, and DELETE operations.
  • Preserve the exact serialized request content without unnecessary overhead.
  • Prevent recursive acquire/replay loops.
  • Surface policy-evaluation and token-acquisition failures clearly.
  • Define tracing, logging, and token-redaction behavior.
  • Decide whether support is default-enabled or explicitly configured.

Expected outcome

Please propose the Java-specific architecture and public API, preferably with a prototype covering:

  • successful 403 → acquirePolicyToken → replay;
  • verification that the original, token-acquisition, and replay payloads are byte-for-byte identical;
  • prevention of payload reserialization;
  • bodyless operations;
  • token-acquisition failure or policy denial;
  • replay-loop prevention;
  • synchronous and asynchronous APIs;
  • integration with the management client pipeline.

The prototype is for design validation and does not need to be production-ready.

主要语言
Java
星标
2.6k
派生
2.2k
平均合并
2 天 1 小时
30 天内合并 PR
238

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

Azure/azure-sdk-for-java 的其他 Issue

查看 Azure/azure-sdk-for-java 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。