Skip to content

Support client_credentials flow with Microsoft Identity Platform v2.0 using client assertions #465

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.

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

Closed
manicminer opened this issue Dec 15, 2020 · 2 comments · May be fixed by #464
Closed

Comments

@manicminer
Copy link

  • Commonly referred to as Client Certificate authentication
  • I'm not sure if this follows a particular standard, but it's similar to client_credentials flow but signing a JWT for identity instead of sending a shared secret
  • Azure AD is the only place I've seen this, so I guess belongs in the microsoft package? Unless there's a standard implementation I missed.

Example/proposal in #464

Documentation

manicminer added a commit to manicminer/golang-oauth2 that referenced this issue Dec 15, 2020
Fixes golang#465

- Commonly referred to as Client Certificate authentication
- Similar to JWT two-legged auth but incompatible
manicminer added a commit to manicminer/golang-oauth2 that referenced this issue Dec 15, 2020
Fixes golang#465

- Commonly referred to as Client Certificate authentication
- Similar to JWT two-legged auth but incompatible
manicminer added a commit to manicminer/golang-oauth2 that referenced this issue Dec 15, 2020
Fixes golang#465

- Commonly referred to as Client Certificate authentication
- Similar to JWT two-legged auth but incompatible
@deltamualpha
Copy link

I would find this very valuable. @codyoss, are you the current maintainer of this package? The pull request here seems quite reasonable.

@manicminer
Copy link
Author

@deltamualpha If you're looking for a maintained implementation of this, I have a package github.com/manicminer/hamilton/auth supporting the various Azure AD authentication methods.

@seankhliao seankhliao closed this as not planned Won't fix, can't repro, duplicate, stale Apr 19, 2025
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 a pull request may close this issue.

3 participants