Skip to content

Create design document for MSI v2 In-Memory Key Approach#905

Open
gladjohn wants to merge 1 commit intodevfrom
gladjohn-patch-2
Open

Create design document for MSI v2 In-Memory Key Approach#905
gladjohn wants to merge 1 commit intodevfrom
gladjohn-patch-2

Conversation

@gladjohn
Copy link
Copy Markdown
Contributor

Add design document for MSI v2 In-Memory Key Approach, detailing goals, .NET reference implementation, Python implementation design, comparison with KeyGuard, and API design.

Add design document for MSI v2 In-Memory Key Approach, detailing goals, .NET reference implementation, Python implementation design, comparison with KeyGuard, and API design.
Copilot AI review requested due to automatic review settings April 17, 2026 19:52
@gladjohn gladjohn requested a review from a team as a code owner April 17, 2026 19:52
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Adds a design document describing an MSI v2 “in-memory/exportable RSA key” approach (as an alternative to the KeyGuard/non-exportable key path), including a .NET reference, proposed Python flow, tradeoffs, and a suggested API surface.

Changes:

  • Introduces a new design doc outlining an exportable, cross-platform MSI v2 key strategy.
  • Provides illustrative Python snippets for key generation, CSR creation, IMDS calls, mTLS token acquisition, and resource calls.
  • Documents a comparison table and proposed API behavior toggling between KeyGuard+attestation vs in-memory.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread docs/msi-v2-in-memory-key-approach.md
Comment thread docs/msi-v2-in-memory-key-approach.md
Comment thread docs/msi-v2-in-memory-key-approach.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants