How to use DiscourseConnect as a client only?

Support SSO

AI-generated summary

Using DiscourseConnect as a Client Only

cosdesign attempted to set up DiscourseConnect to allow website visitors to log in and register with Discourse, but encountered a 404 error.

RGJ pointed out that the DiscourseConnect settings were configured incorrectly, allowing Wordpress to authenticate instead of Discourse. To fix this, RGJ advised removing the DiscourseConnect settings on Discourse and making changes in Admin - Settings - Login.

After making the changes, cosdesign was able to resolve the issue. However, they noted that the settings can be confusing, particularly the DiscourseConnect Provider option, which is worded oppositely on the WP DiscourseConnect Provider tab.

1

Hello, I would like my website visitors to only be able to log in and register with Discourse. Here’s what I did so far (but it gives me a 404 error).

Step 1: I created the DiscourseConnect Secret Key
Step 2: Enabled these options on my WP website

wp-discourse-client_step1
wp-discourse-client_step1819×532 31.8 KB

Step 3: Enabled these options on Discourse:

wp-discourse-client_step2
wp-discourse-client_step2786×675 33.6 KB

Step 4: Visited the wp-login.php and if I press the Log in with Discourse link or if I use this shortcode [discourse_connect_client] on any page, it gives me a 404 error on Discourse.

What am I missing?

wp-discourse-client_step3
wp-discourse-client_step3498×468 8.39 KB

Any help is appreciated.

2

You have configured Discourse as if it would use Wordpress to authenticate, which is not what you want to do.

You should remove all DiscourseConnect settings you’ve made on Discourse side and make the following settings in Admin - Settings - Login instead:

image
image744×230 17.6 KB

3

Thanks for your help, now is working. And btw I was getting this error because I pasted my website URL with https:// in front (it should be just yourwebsite.com):

“Authentication failed due to missing secret. Contact the site administrators to fix this problem.”

And I must say that these settings are a bit confusing. As in your image, I should’ve enabled the Discourse Connect Provider option on Discourse, although the DiscourseConnect Provider tab on WP says the opposite of what I wanted:

" Enabling your site to function as the DiscourseConnect provider transfers all user authentication from Discourse to WordPress.".

They should be renamed and or/separated by a title or maybe on different tabs as they are on WordPress.