Proof of Presence (PoP) for Pull Requests – Re-authentication on PR merge & approval (Entra IdP) [Public Preview]

未关闭
#1,320 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
冷清
技术栈
azure

调研方向

此路线图 issue 描述了通过 Microsoft Entra ID 对 pull request 批准和合并实施 Proof of Presence,但没有指出任何 repository 文件、测试或实现入口点。首先定位 pull request 批准和合并的身份验证流程;当已配置的策略在任一操作完成之前触发新的交互式 MFA 挑战时,即视为完成。

由索引模型根据 Issue 内容生成。

描述

Enterprise Public Preview
Value Prop

When a repository policy requires it, developers approving or merging a pull request are prompted to complete a fresh, interactive MFA challenge through Microsoft Entra ID before the action goes through. This ensures that the specific person taking those high-impact actions is genuinely present and verified at the exact moment they matter — not just holding an active session. It adds a meaningful layer of identity assurance directly into the pull request workflow, without changing how teams collaborate day to day.

Expected Outcome

Regulated organizations can now demonstrate, with a real-time identity check, that pull request approvals and merges were performed by an authorized, present individual — strengthening compliance with requirements like FDA 21 CFR Part 11. By anchoring proof of presence to the two most consequential points in the code review process, teams reduce the risk that compromised tokens or sessions could silently influence what ships to production.

主要语言
没有语言数据
星标
9k
派生
1.8k
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

github/roadmap 的其他 Issue

查看 github/roadmap 的全部 Issue

相似的 Issue

更多 Security Issue

把新 issue 发到你的邮箱

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