Invalid request - new plugin installation and setup


(Homebrew Hops) #1

I have followed the steps outlined for installation and setup of wp-discourse. Pinned here and on the wp-discourse git wiki.

When I navigate to my discourse forum and click login, I am presented with the wordpress login screen. After entering credentials, the page displays invalid request and the url reads:

http://wordpress.domain.com/login?sso=bm9uY2U9ZjkxYzRhM2FhMDZmYjY0YzQ3NTUxOWU0YTk2YjY5MDMmcmV0dXJuX3Nzb191cmw9aHR0cCUzQSUyRiUyRmZvcnVtLnBpZGdlLm5ldCUyRnNlc3Npb24lMkZzc29fbG9naW4%3D&sig=9d98737440c1fdbdfdf8f2485e30cb1548f7ee929ce9e28194442f48c239647c

Where do I begin to check for what might be going wrong?


(Simon Cossar) #2

Have you set the ‘sso secret’ on both the Discourse forum and on WordPress? They need to be set to the same value.


(Homebrew Hops) #3

Yay! It was a mismatched secret! Thank you!


#4

I would just like to add to this, I was having the same exact issue as @homebrewhops with the sso redirecting to login page, and after logging in seeing “invalid request” In my case however., I did not have a mismatched secret. The secret I was using was: DT>ZMF7a6Q$WesK . The Wordpress discourse plugin specifies:

The secret key used to verify Discourse SSO requests. Set it to a string of text, at least 10 characters long. It needs to match the key set at https://forum.oilsgift.com/admin/site_settings/category/all_results?filter=sso.

one or several of the characters used in my SSO Secret Key was causing the error. So do make sure that it is a “string of text” as specified, also numbers did work for me, so just the special characters should be avoided.

The PrimeTime WordPress + Discourse SSO plugin had no problem authenticating with this same SSO key, so I’m certain the ability to use special characters could be implemented into the official Discourse App.

Anyway I hope this may help someone that is having trouble as I did and can save you some time. Good Luck.


(Simon Cossar) #5

DT>ZMF7a6Q$WesK should work for the SSO secret. If a space is added at the start or the end of the key, the plugin isn’t stripping the space. Discourse does trim spaces when it saves the key. Maybe that was the problem.


#7

It could be that it was related to something else, because I did make sure that there were no spaces at the beginning or left at the end of the key on both the Wordpress and Discourse sides. I do have a custom wp-login.php that things get redirected to so maybe that was the issue?


(Stephen) #8

Have you customised wp-login.php directly or just modified login from your theme’s functions.php


#9

I added a rewrite rule to the .htaccess file:

RewriteRule ^wp-signup.php(.*)$ wp-content/themes/divi-child/wp-signup.php$1

and after copying over the wp-signup.php to the child theme, made a few edits, but that was just to text on the page no code.