Jump to content

OAuth problem | Invalid Redirection URI/Fehlercode: 2S361/2


Tim Schmidt

Recommended Posts

Posted

Hi,

i installed a new forum and a website based on wordpress. Now i m trying to connect both.

I want to use the forum as the OAuth Server and the Wordpress site as client.

I used the offical guide and completed all of the nessesary task (i hope i did ;D). Well it seems that i missed something.

When i want to login into the Wordpress site or test the OAuth connection following error shows up.

 

invision.png

Posted

If Wordpress is the client, you need to enter the Wordpress redirect URI into the AdminCP. I'm unclear when you say you took the information from the AdminCP if you are referring to the Wordpress control panel or not, but based on your description of what you are trying to set up, you need to create an OAuth client in the AdminCP (under Rest & OAuth), and when prompted for the redirect URI you need to enter the correct one for your Wordpress installation.

Be sure you match http and https, and trailing slash or no trailing slash. The URL must match exactly.

Posted
On 11/9/2018 at 7:18 PM, Tim Schmidt said:

I made those screenshot, i think they match? 😕

Or is the www. a problem?

wordpress.png

invisioncom.png

The Invision Community form is asking for the WordPress Site URL, not the callback URL. Try changing that and it should work.

  • 3 weeks later...
Posted
On 11/17/2018 at 8:47 PM, Tim Schmidt said:

Sorry for the late reply, was in london =).

When i typ the wordpress url, invision changes it to .../oauthcallback

Can i push it? Still not working 😞

  • 1 month later...
Posted

Thank you bfarber, i created a support ticket.

I manually changed the redirect url in the mysql database and it works, more or less :D.

Now i get following error, when i try to login.

{"error":"invalid_client"}invalid_client

Posted

I too had his problem. It's definitely a simple bugfix on the IPS side. I'll demonstrate:

If you enter your Wordpress site URL as shown, then click Save.....

756222997_ScreenShot2019-01-20at4_15_13PM.thumb.png.72c4015c6cf335c3a9335bed1ee868f4.png

 

.....it will automatically add /oauthcallback to it, as shown when you re-open the settings:

618433301_ScreenShot2019-01-20at4_15_24PM.thumb.png.aa874ec92a438902b3fcfa9df150e7c2.png

 

....in fact if you save and close.....and save and close again.....it will have added FOUR /oauthcallback trailing slashes!

 

Opened the database to check, and sure enough it was a wonky entry:

72840193_ScreenShot2019-01-20at4_19_34PM.thumb.png.9ae3c3a9a3c333e79bb98f5f5ac55366.png

Had to manually change it, and then everything worked!

1521378942_ScreenShot2019-01-20at4_22_02PM.png.4a9aa22dcd515587c60e6ab071552161.png

However you have to be careful not to open up those OAuth client settings, otherwise it messes everything up again. 

Hey @bfarber Hopefully the fine folks at IPS can fix this little bug! 


*UPDATE*: @Tim Schmidt I get the same error after: {"error":"invalid_client"}invalid_client

 

Posted
10 hours ago, Neville1 said:

I too had his problem. It's definitely a simple bugfix on the IPS side. I'll demonstrate:

If you enter your Wordpress site URL as shown, then click Save.....

756222997_ScreenShot2019-01-20at4_15_13PM.thumb.png.72c4015c6cf335c3a9335bed1ee868f4.png

 

.....it will automatically add /oauthcallback to it, as shown when you re-open the settings:

618433301_ScreenShot2019-01-20at4_15_24PM.thumb.png.aa874ec92a438902b3fcfa9df150e7c2.png

 

....in fact if you save and close.....and save and close again.....it will have added FOUR /oauthcallback trailing slashes!

 

Opened the database to check, and sure enough it was a wonky entry:

72840193_ScreenShot2019-01-20at4_19_34PM.thumb.png.9ae3c3a9a3c333e79bb98f5f5ac55366.png

Had to manually change it, and then everything worked!

1521378942_ScreenShot2019-01-20at4_22_02PM.png.4a9aa22dcd515587c60e6ab071552161.png

However you have to be careful not to open up those OAuth client settings, otherwise it messes everything up again. 

Hey @bfarber Hopefully the fine folks at IPS can fix this little bug! 


*UPDATE*: @Tim Schmidt I get the same error after: {"error":"invalid_client"}invalid_client

 

Thank you, yes i did the change manually in the database :).

When you login 3 times with the error: {"error":"invalid_client"}invalid_client
You ll get banned :D.

Posted

They have a ticket with the oauth redirect url, the next problem is still unsolved and won't be solved with the basic support 😞

{"error":"invalid_client"}invalid_client

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...