# 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:** 8

<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,‏ 4:56pm UTC](https://meta.discourse.org/t/oauth2-and-microsoft-adfs/103357/8 "2018-12-03T16:56:21Z")

</div>

Thanks, so it looks like there is a userinfo endpoint specified in the document. Since it is specified, the plugin will try and use it to collect metadata about the user, rather than using the data in the token. It sounds like ADFS is issuing a token which does not have permission to access the userinfo URL. That might be configurable, but I’m afraid I don’t know anything about ADFS.

If that can’t be fixed, I can add a configuration option to the plugin so that you can force the plugin to ignore the userinfo endpoint - it sounds like this could be a useful preference for other people as well.

---

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