Proof of Presence (PoP) for Pull Requests – Re-authentication on PR merge & approval (Entra IdP) [Public Preview]
- Dominant language
- No language data
- Stars
- 8.9k
- Forks
- 1.8k
- PR merge metrics
- No merged PRs in 30d
Description
### 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.
Contributor guide
Research direction
This roadmap issue describes Proof of Presence for pull request approvals and merges through Microsoft Entra ID, but it names no repository files, tests, or implementation entry points. Start by locating the pull request approval and merge authentication flows; done would mean the configured policy triggers a fresh interactive MFA challenge before either action completes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100