# Error using discourse-oauth2-basic plugin with NeonCRM

**URL:** <https://meta.discourse.org/t/error-using-discourse-oauth2-basic-plugin-with-neoncrm/132596>\
**Category:** SSO\
**Tags:** oauth2\
**Created:** [November 5, 2019, 12:18am UTC](https://meta.discourse.org/t/error-using-discourse-oauth2-basic-plugin-with-neoncrm/132596 "2019-11-05T00:18:43Z")\
**Posts on this page:** 1\
**Showing post:** 32

<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:** [February 7, 2020, 7:36pm UTC](https://meta.discourse.org/t/error-using-discourse-oauth2-basic-plugin-with-neoncrm/132596/32 "2020-02-07T19:36:50Z")

</div>

Denis and I worked out that NeonCRM aren’t really sticking to the oauth2 spec… they are sending the user\_id inside the access\_token variable, and it cannot be used as an actual access token.

So, you need to disable oauth2\_fetch\_user\_details, and set oauth2\_callback\_user\_id\_path to `token` (not access\_token, because the oauth2 ruby library renames it for internal use)

With that, it should be functional, but there is no way to fetch the user email/name

---

_[View the full topic](https://meta.discourse.org/t/error-using-discourse-oauth2-basic-plugin-with-neoncrm/132596)._
