Special thanks to @dashohoxha for his help!! Continuing the discussion from OAuth2 Basic Support: I will use this thread to document my steps and progress in integrating Discourse and Drupal via OAuth2. At present, the status of my implementation is WORKING. Installation on Discourse: For installation on Discourse, do the following: Install OAuth2 Basic plugin as per this thread. See Install a plugin for details on how to install a plugin Configure OAuth2 plugin: You should see an “OAuth2” section in “Login” in Settings when logged in as an administrative user. Enable “Custom OAuth2 is enabled” Set client ID as “discourse”. Create a client secret that is a random series of letters and numbers. You can use apg -a 0 -m 20 to generate one. oauth2 authorize url: https://DRUPAL/oauth2/authorize where DRUPAL = your Drupal site’s base URL oauth2 token url: https://DRUPAL/oauth2/token oauth2 user json url: https://DRUPAL/oauth2/user_profile.json oauth2 json user id path: uid oauth2 json username: name oauth2 json name path:[ You can leave this blank] oauth2 json email path: mail oauth2 email verified: [Check this on] When you hit ‘login’, you should now see a ‘login with OAuth2’ option. Installation on Drupal Install the following plugins: OAuth2 Login Provider OAuth2 Server Services REST Server Add client at /oauth2-servers/manage/oauth2/clients Call the client discourse Enter the same client secret as above Set Redirect URIs as http://DISCOURSE/auth/oauth2_basic/callback where DISCOURSE = your discourse forum’s base URL Status and Known Issues: If you follow the steps above, you should see a “with OAuth2” badge on the login screen. Clicking on it should redirect you to your Drupal site for login that asks “Authorize discourse to use your account?” Clicking “Yes” results in either association to an existing account with the same email or creation of a new account with that email. STATUS: WORKING KNOWN ISSUES: Must be authorized with each login. Does not honour ‘groups’ / ‘roles’ tarek : )

[image] tarek: I’m not sure how to figure out the output of user/profile in OAuth2_loginprovider The output should be a JSON that contains the fields of the user profile. Can you print it somewhere for debugging? I am not familiar with RoR, so I cannot help you with this.

I really have no idea how to debug RoR either. I’m trying now to figure that out.. Currently, that looks like where I’m stuck. I also am having no luck trying to manually get the data out with a REST client.. What do you use to test? tarek : )

[image] tarek: What do you use to test? For testing I use this: http://info.btranslator.org/api-examples-js/ See the section OAuth2/user/profile (on the left). Then check the javascript code and the output.

I have extended the Drupal module to accept both POST /oauth2/user/profile and GET /oauth2/user_profile (see the description at Client Challenge).

WOW WOW WOW!!! That’s so wonderful! Thank you so much!! Now I’m just trying to figure out where each path is, and then I’ll update above. tarek : )

I have updated the first post with the new error. In essence, Drupal is NOT giving json, but IS giving XML. Here is the output: 757: unexpected token at ' 555 testuser testuser@testuser.org 1273090 1465263 1462493892 1 23 0 picture-555-profile.png public://pictures/picture-picture-555-profile.png image/png 206962 1 14164658 https://DRUPAL/sites/DRUPAL/files/pictures/picture-555-profile.png t We are way closer now!! Thank you! tarek : )

GOT IT!!! just needed a .json at the end! Will update above! tarek : )

[image] tarek: Drupal is NOT giving json, but IS giving XML This is related to the configuration of the Drupal module Services at /admin/structure/services/list/oauth2_login_provider/server By default all types of request and response formats are enabled, and if the HTTP request does not specify a response format, XML is used by default. Either you can restrict this on the server, or make the client specify that they want JSON. In one of my JavaScript example I do it like this: B-Translator.github.io/api-examples-js/examples/oauth2/get_user_profile.js at master · B-Translator/B-Translator.github.io · GitHub Apparently it also works if you append the extension .json to the URL (you discovered this). As long as it works, it is fine.

[image] dashohoxha: In one of my JavaScript example I do it like this: B-Translator.github.io/api-examples-js/examples/oauth2/get_user_profile.js at master · B-Translator/B-Translator.github.io · GitHub I tried this and could not get it to work, neither in my own REST client, nor in your b-translator, as dataType will always default to json (I tried ‘xml’, for example). Regardless, mercifully this is behind me! I also got my Kunena posts redirected, which is also merciful. So no problems! tarek : )

[image] tarek: I tried this and could not get it to work, neither in my own REST client, nor in your b-translator, as dataType will always default to json (I tried ‘xml’, for example). Maybe you did not clear the cache in Drupal, and maybe the javascript client is smarter than we think (it handles the data type conversions behind the scenes). Anyway this doesn’t matter.

OAuth2 integration with Drupal

Product Support SSO

pfaffman (Jay Pfaffman) August 4, 2017, 12:18pm 27

It takes extra steps to have roles and groups passed via SSO. By default SSO just handles authentication. You can then assign roles and groups by hand in Discourse.

Topic		Replies	Views
Discourse OAuth2 Basic Plugin official , oauth2 , auth-plugins , included-in-core	30	68320	July 24, 2025
How to use Oauth2 service provided by discourse? SSO oauth2	1	1993	June 15, 2020
Trouble connecting drupal and discourse Product Support	7	6592	October 18, 2017
Can I authenticate to Drupal via Discourse? Product Support	4	1822	October 25, 2019
Login to Discourse with custom Oauth2 provider Feature oauth2 , completed	22	274541	July 6, 2020

OAuth2 integration with Drupal

Related topics