# OAuth2 and Microsoft ADFS

**URL:** <https://meta.discourse.org/t/oauth2-and-microsoft-adfs/103357>\
**Category:** Product Support\
**Created:** [3 בדצמבר,‏ 2018,‏ 2:49pm UTC](https://meta.discourse.org/t/oauth2-and-microsoft-adfs/103357 "2018-12-03T14:49:42Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [3 בדצמבר,‏ 2018,‏ 3:11pm UTC](https://meta.discourse.org/t/oauth2-and-microsoft-adfs/103357/3 "2018-12-03T15:11:55Z")

</div>

I am not familiar with ADFS, but I have just finished setting up an integration with Azure B2C, which is likely very similar.

It looks like ADFS supports openid\_connect: [Migrate to the Microsoft Authentication Library (MSAL) - Microsoft identity platform | Microsoft Learn](https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/development/enabling-openid-connect-with-ad-fs)

So in theory, you can use the new [discourse-openid-connect](https://github.com/discourse/discourse-openid-connect) plugin. After completing the setup on the ADFS end, you just input the ‘discovery document’ URL into Discourse, along with the client id/secret. If the discovery document does not contain a “user info endpoint”, then the user information will be extracted from the JSON Web Token obtained from the “token endpoint”.

I will be adding some documentation for this new openid connect plugin this week, so please do let me know if you get it working for ADFS!

---

_[View the full topic](https://meta.discourse.org/t/oauth2-and-microsoft-adfs/103357)._