8000 MSAL node PoP support · Issue #5082 · AzureAD/microsoft-authentication-library-for-js · GitHub
[go: up one dir, main page]
Skip to content

MSAL node PoP support #5082

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
aleknik opened this issue Aug 5, 2022 · 4 comments
Closed

MSAL node PoP support #5082

aleknik opened this issue Aug 5, 2022 · 4 comments
Assignees
@EmLauber
Labels
feature Feature requests. msal-node Related to msal-node package tracked-internally Bugs that are tracked by Msft internally

Comments

@aleknik
Copy link
aleknik commented Aug 5, 2022

Core Library

MSAL Node (@azure/msal-node)

Core Library Version

1.12.0

Wrapper Library

Not Applicable

Wrapper Library Version

none

Description

Hey team,

Is it possible to get a PoP protected token using client credential flow in msal node?

MSAL Configuration

No response

Relevant Code Snippets

No response

Identity Provider

No response

Source

Internal (Microsoft)
@aleknik aleknik added the question Customer is asking for a clarification, use case or information. label Aug 5, 2022
@ghost ghost assigned jasonnutter Aug 5, 2022
@ghost ghost added the Needs: Attention 👋 Awaiting response from the MSAL.js team label Aug 5, 2022
@github-actions github-actions bot added the msal-node Related to msal-node package label Aug 5, 2022
@jasonnutter
Copy link
Contributor

@aleknik This is in our backlog, unsure about ETA. @EmLauber

@ghost ghost added answered Question has received "first qualified response" Needs: Author Feedback Awaiting response from issue author and removed Needs: Attention 👋 Awaiting response from the MSAL.js team labels Aug 5, 2022
@jasonnutter jasonnutter added feature Feature requests. experimental Needs: Attention 👋 Awaiting response from the MSAL.js team tracked-internally Bugs that are tracked by Msft internally and removed answered Question has received "first qualified response" Needs: Author Feedback Awaiting response from issue author labels Aug 5, 2022
@ghost ghost removed question Customer is asking for a clarification, use case or information. Needs: Attention 👋 Awaiting response from the MSAL.js team labels Aug 5, 2022
@EmLauber
Copy link
Contributor
EmLauber commented Aug 5, 2022

@aleknik we don't have an ETA but are looking into this. Are you Microsoft internal? If so we should connect on a possible private preview. CC: @medhir

@jasonnutter jasonnutter removed their assignment Aug 9, 2022
@bgavrilMS
Copy link
Member

@aleknik - can you contact us directly via email ? POP is not ready for 3p at this point, but we can work with you to understand your 1p scenario.

@bgavrilMS
Copy link
Member

I am going to close this. We are looking at enabling mtls POP - https://datatracker.ietf.org/doc/html/rfc8705 for client credentials flow. We do not have a solution at this point.

@bgavrilMS bgavrilMS closed this as not planned Won't fix, can't repro, duplicate, stale May 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@EmLauber EmLauber

Labels
feature Feature requests. msal-node Related to msal-node package tracked-internally Bugs that are tracked by Msft internally
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@jasonnutter @aleknik @bgavrilMS @EmLauber
0