docs(design): devex proposal for mTLS PoP on Managed Identity and FIC - #3832
Merged
Conversation
Add specification for mTLS Proof-of-Possession support in Microsoft.Identity.Web for Managed Identity and Federated Identity Credential.
This was referenced Jun 1, 2026
cpp11nullptr
reviewed
Jun 8, 2026
cpp11nullptr
reviewed
Jun 8, 2026
cpp11nullptr
approved these changes
Jun 8, 2026
gladjohn
pushed a commit
that referenced
this pull request
Jun 8, 2026
Implements devex spec #3832: - TokenAcquisition: chain WithMtlsProofOfPossession().WithAttestationSupport() on the pure-MI builder when ProtocolScheme=MTLS_POP. - ConfidentialClientApplicationBuilderExtension: dispatch FIC-with-MI to a bound-assertion delegate that returns ClientSignedAssertion (carrying both the JWT and the MI-minted binding certificate). All other signed-assertion source types still throw IDW10115 (preserved by regression test). - ManagedIdentityClientAssertion: new internal GetSignedAssertionWithBindingAsync that calls AcquireTokenForManagedIdentity(...).WithMtlsProofOfPossession() .WithAttestationSupport() and returns the bound assertion + cert pair. - Reference Microsoft.Identity.Client.KeyAttestation 4.84.1-preview. - IVT from Certificateless to TokenAcquisition (3rd entry in established file). - 2 new unit tests in WithClientCredentialsTests.cs (930 total pass, 0 fail). - 2 new daemon samples: daemon-app-msi-mtls, daemon-app-fic-mtls. No new public API surface. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
bgavrilMS
reviewed
Jun 9, 2026
| ```json | ||
| { | ||
| "AzureKeyVault": { | ||
| "BaseUrl": "https://contoso.vault.azure.net/", |
Member
There was a problem hiding this comment.
I assume the AKV url changes to an mtls specific endpoint?
gladjohn
added a commit
that referenced
this pull request
Jun 10, 2026
#3839) * Add MSI mTLS PoP support: pure MI + FIC-with-MI Implements devex spec #3832: - TokenAcquisition: chain WithMtlsProofOfPossession().WithAttestationSupport() on the pure-MI builder when ProtocolScheme=MTLS_POP. - ConfidentialClientApplicationBuilderExtension: dispatch FIC-with-MI to a bound-assertion delegate that returns ClientSignedAssertion (carrying both the JWT and the MI-minted binding certificate). All other signed-assertion source types still throw IDW10115 (preserved by regression test). - ManagedIdentityClientAssertion: new internal GetSignedAssertionWithBindingAsync that calls AcquireTokenForManagedIdentity(...).WithMtlsProofOfPossession() .WithAttestationSupport() and returns the bound assertion + cert pair. - Reference Microsoft.Identity.Client.KeyAttestation 4.84.1-preview. - IVT from Certificateless to TokenAcquisition (3rd entry in established file). - 2 new unit tests in WithClientCredentialsTests.cs (930 total pass, 0 fail). - 2 new daemon samples: daemon-app-msi-mtls, daemon-app-fic-mtls. No new public API surface. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Address review feedback: rename effectiveToken; bump KeyAttestation to GA 4.84.2 - Rename CancellationToken variable per cpp11nullptr review feedback to avoid confusion with OAuth/auth tokens (effectiveToken -> effectiveCancellationToken in GetSignedAssertionWithBindingAsync). - Bump Microsoft.Identity.Client.KeyAttestation from 4.84.1-preview to GA 4.84.2 so it aligns with MSAL 4.84.2 already on master. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * address pr comments --------- Co-authored-by: gladjohn <gladjohn@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This was referenced Jun 24, 2026
Merged
Closed
Closed
This was referenced Jul 17, 2026
Closed
Closed
Closed
This was referenced Jul 27, 2026
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Merged
Merged
This was referenced Aug 3, 2026
Open
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a developer-experience design document for enabling mTLS Proof-of-Possession (mTLS PoP) on the two managed-identity credential sources that currently don't support it:
AcquireTokenOptions.ManagedIdentity(pure Managed Identity)SignedAssertionFromManagedIdentity(Federated Identity Credential signed by a Managed Identity)The doc lives at
docs/design/msi_fic_mtls_pop_devex.md, alongside the existingmanaged_identity_capabilities_devex.md.Why
Microsoft.Identity.Webalready supports mTLS PoP for confidential client apps that authenticate with a certificate (seetoken-binding.md). The opt-in is one line of configuration:The same opt-in does not work today for the two managed-identity credential sources:
SignedAssertionFromManagedIdentity(FIC)AcquireTokenOptions.ManagedIdentity(MSI)This is the gap the proposal closes.
What's in scope
"ProtocolScheme": "MTLS_POP"knob enables mTLS PoP for all three credential sources.daemon-app-msi-mtlsanddaemon-app-fic-mtls, modeled on the existingdaemon-app-msi.token-binding.md(add MI + FIC subsections) andcertificateless.md(add a short cross-ref).What's out of scope
token-binding.md.Prerequisites for the implementation PR
Microsoft.Identity.Webtakes a dependency onMicrosoft.Identity.Client.KeyAttestation(GA in the next MSAL release).