Hi there, I´m working for a big company and I´m using an internal oauth2 provider in conjunction with this plugin. In a different business unit there is already another discourse instance running, where the same setup works. I analyzed their instance, and found almost nothing except a version difference of the plugin and of discourse itself. But first of all I´ll tell you what happens. I set up the plugin and configured everything according to documentation (the same as the other instance plus some settings, which aren´t available in the old version (0.2) of the plugin which they are using. No I see the extra button in login screen and get forwarded to a login page (company) where I can type in my SSO account & pw… After pressing enter this screen appears: [image] The logs show this: (oauth2_basic) Authentication failure! invalid_credentials: OAuth2::Error, invalid_client: Invalid authentication method for accessing this endpoint. {"error_description":"Invalid authentication method for accessing this endpoint.","error":"invalid_client"} I double checked the credentials and talked with the guys of web-eam support, and they said the authorization phase was succcessful (I got valid return parameters (code, iss, state) with the callback call) Anyone knows how to approach this problem ? My versions are: Discourse: v2.3.0.beta5 +5 oauth-basic plugin: 0.3 Many thanks in advance and greetings, Wurzelseppi

Do you have verbose SSO logging mode enabled in your site settings when testing?

Hi, sure I have :slight_smile: Do I get the verbose logs then also over the log-viewer, or do I have to dig deeper in my container ?

See /var/discourse/shared/standalone/logs/rails

It says there (oauth2_basic) Setup endpoint detected, running now. (oauth2_basic) Callback phase initiated. (oauth2_basic) Authentication failure! invalid_credentials: OAuth2::Error, invalid_client: Invalid authentication method for accessing this endpoint. {"error_description":"Invalid authentication method for accessing this endpoint.","error":"invalid_client"} Started GET "/auth/failure?message=invalid_credentials&origin=https%3A%2F%2F[community-address]%2F&strategy=oauth2_basic" for 127.0.0.1 at 2019-03-21 10:50:43 +0000 Processing by Users::OmniauthCallbacksController#failure as HTML Parameters: {"message"=>"invalid_credentials", "origin"=>"https://[community-address]/", "strategy"=>"oauth2_basic"} The support guys told me, that the invalid client message doesn´t come from their end…

Hi, hmmm..do you have any clue where i could do that ?

Serve Discourse from a subfolder (path prefix) instead of a subdomain has an example.

Probably I´m to dense to understand it :smiley: , but I found nothing in that link you mentioned which is related to this

Maybe How to set set_real_ip_from for discourse - #9 by parisa will be more helpful.

Hi, is it possible to roll back to previous version ? A neighbouring instance is using 0.2, and I 0.3 … mine doesn´t work, theirs do … Just want to make sure it hass nothing to do with the new version. Thanks guys!

Sorry, there was an error authorizing your account

Product Support SSO

pfaffman (Jay Pfaffman) March 21, 2019, 11:43am 6

I don’t know if it’s related, but the ip address is localhost, which suggests that you need to modify your setup to get the correct remote ip number reported to discourse.

Topic		Replies	Views
Discourse OAuth2 Basic Plugin official , oauth2 , auth-plugins , included-in-core	30	68451	July 24, 2025
Making SSO via OAuth2 Basic plugin work with our Identity Provider SSO oauth2	1	4435	May 9, 2018
OAUTH2 basic - a nightmare :-( SSO oauth2	20	1141	December 3, 2024
Error using discourse-oauth2-basic plugin with NeonCRM SSO oauth2	28	5387	February 12, 2020
Error during SSO integration - Wholistic Minds Product Support	5	1312	June 24, 2021

Sorry, there was an error authorizing your account

Related topics