PHP and WordPress Single Sign On (SSO) with optional JWT Addon

maicol07

temey74938 not at the moment. I'm working on an update to make it compatible with beta 16. Stay tuned!

temey74938

maicol07 Thank you for your prompt reply.

maicol07

Warning! If anyone has tried to buy premium addons from the docs buttons they were not working!! Now I've fixed them and they work as normal!

maicol07

Progress update #1 (beta16)

I've decided to do some progress updates sometimes, when I'm working on a new version of the extension. This time, two things to announce:

With this first progress update we reached 400 posts in this thread. This means the extension (and my coding experience) has grown and became better at every update! Thank you guys!
Next update that enables compatibility with beta16 is coming soon and it's really near! Prepare for some breaking changes in the PHP plugin and in the JWT plugin. I need only to do some more testing, fixing a bug and write docs for the new version. Stay tuned!

Progress update finished!
Happy Easter everyone!

maicol07

This time, since release notes are bigger than the previous releases, I'll add the links to the changelog and upgrading guide (if exists). Tell me if you like this format and you want it for the next releases and the new changelog format in the docs.

Release 1.9 (Extension)

📝 Changelog

Release 3.0 (PHP Plugin)

There are some breaking changes in this release, so be sure to check the upgrade guide below.
📝 Changelog
🔖 Upgrading guide (Version specific upgrade notes)

Release 2.1 (WP Plugin)

WP plugin will take a little longer to come up as update. ~~Wait 10 minutes or so from now~~ WP SVN has some issues, I'll try to upload the new version to WP repo tomorrow. If you want to upgrade use the manual method explained in the installation docs.

✨ Update to PHP plugin v3
🐛 Fixed a bug where deactivating the plugin from WP dashboard caused a fatal error (FSSOE-16)

All the addons of the two plugins have been updated to support beta16 and its plugin changes

UaMV and SportDevAdam please try this new version to see if your issue is fixed

ctml

maicol07 thanks for the update, time for me to upgrade to beta 16 😀

UaMV

maicol07 please try this new version to see if your issue is fixed

Just got them up and running – working like a charm! However, I did have to install the WP plugin via GitHub since the WP directory didn't seem to yet have v2.1.

Thank you! 💯

UaMV

Encountered the following when attempting to bulk delete a few test users on my site:

An error of type E_ERROR was caused in line 113 of the file /home/…/wp-content/plugins/sso-flarum/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php. Error message: Uncaught GuzzleHttp\Exception\ServerException: Server error: `DELETE https://…/api/users/1` resulted in a `500 Internal Server Error` response:
{"errors":[{"status":"500","code":"unknown","detail":"DomainException: Cannot delete the root admin in \/home\/[redacted] (truncated...)
 in /home/…/wp-content/plugins/sso-flarum/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:113
Stack trace:
#0 /home/…/wp-content/plugins/sso-flarum/vendor/guzzlehttp/guzzle/src/Middleware.php(69): GuzzleHttp\Exception\RequestException::create()
#1 /home/…/wp-content/plugins/sso-flarum/vendor/guzzlehttp/promises/src/Promise.php(204): GuzzleHttp\Middleware::GuzzleHttp\{closure}()
#2 /home/…/wp-content/plugins/sso-flarum/vendor/guzzlehttp/promises/src/Promise.php(153): GuzzleHttp\Promise\Promise::callHandler()
#3 /home/…/wp-content/plugins/sso-flarum/vendor/

maicol07

UaMV ~~from the WP dashboard?~~
I've reproduced the issue and found a fix. You can find the latest 2.1.1 in the Github releases. It seems WP plugin directory has some compatibility issues with my code, so I'm getting in touch with the WP team to solve this.

Sanyu

I recently installed your plugin and I wanted to thank you for the work you put in!
However I did encounter a fatal error but I'm not sure if it's something I did or an error in the plugin.

I installed version 2.1.1 via Github and when I was editing the Edit Account Page with the Woocommerce plugin, I found out that it gives a fatal error when I'm updating a field (in this case the "Display Name/Nickname" Field).

Fatal error: Uncaught GuzzleHttp\Exception\ServerException: Server error: 'PATCH https://[websitedomain]//api/users/7' resulted in a '500 Internal Server Error' 
response: {"errors":[{"status":"500","code":"unknown"}]} in /home/[redacted]/wp-content/plugins/sso-flarum/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:113 

Stack trace: 
#0 /home/[redacted]/wp-content/plugins/sso-flarum/vendor/guzzlehttp/guzzle/src/Middleware.php(69): GuzzleHttp\Exception\RequestException::create() 
#1 /home/[redacted]/wp-content/plugins/sso-flarum/vendor/guzzlehttp/promises/src/Promise.php(204): GuzzleHttp\Middleware::GuzzleHttp\{closure}() 
#2 /home/[redacted]/wp-content/plugins/sso-flarum/vendor/guzzlehttp/promises/src/Promise.php(153): GuzzleHttp\Promise\Promise::callHandler() 
#3 /home/[redacted]/wp-content/plugins/sso-flarum/vendor/guzzlehttp/promises/src/TaskQueue.php(48): GuzzleHttp\Promise\Promise::GuzzleHttp\Promise\{closure}() 
#4 /home/r in /home/[redacted]/wp-content/plugins/sso-flarum/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php on line 113

maicol07

Sanyu it seems your Flarum has an error on the PATCH endpoint. I don't think it's an error related to the extension. Can you try to see the output of that endpoint with a manual request? For example using hoppscotch or postman (or any other API client)

Sanyu

maicol07 The problem is fixed now. I forgot to setup the URL rewriting in Apache so that caused the problem. Thanks for the suggestion!

limatheus

@maicol07 First of all, thank you so much for your work, it's amazing.
I'm faccing some issues with a integration between a existing Laravel 7 application and a fresh version of Flarum.
I'm using version 2.0 of flarum-sso-plugin (laravel side), everything seens to be OK, I can log with my laravel user, call SSO login through a login listener.
apparently everything works without errors, I don't get any messages or errors.
However when accessing the Flarum URL nothing happens the user is not logged in on the forum side.
How do i know that the login worked?
Seeing on access_tokens table the token is there with last_user_agent "Maicol07 Flarum Api Client"
My installation follows this pattern, app.domain.com and Flarum installed on forum.domain.com.
My configuration is bellow

[
            'url' => env('FLARUM_URL'), // http://forum.domain.com
            'root_domain' => env('FLARUM_ROOT') //domain.com,
            'api_key' => env('FLARUM_API_KEY') //40CharsRandomKey,
            'password_token' => env('FLARUM_PASSWORD_TOKEN')  //40CharsRandomKey,
            'verify_ssl' => false //just to avoid this verification
        ];

What I'm missing, can you help me?

maicol07

limatheus hi, are you using beta16? You have to use the version 3.0 of the plugin (on your SSO system) which is only compatible with Laravel 8. Please upgrade to Laravel 8 (shouldn't take too much. I've done it myself back in September when Laravel 8 was released)

UaMV

Hmm. 🤔 Have we seen this one before?

Server error: `POST https://wire.gravityhopper.com/api/users` resulted in a `500 Internal Server Error` response:
{"errors":[{"status":"500","code":"unknown","detail":"PDOException: SQLSTATE[23000]: Integrity constraint violation: 106 (truncated...)

This is about all I'm able to find as a lead – How Can i solved this error:SQLSTATE[23000]: Integrity constraint violation: 1062 …

You able to identify what this may be? Happy to provide anything from my end.

maicol07

UaMV no, that's new. You should catch manually the exception and echo the body to see the full error. This is a Flarum database error so some table may be messed up

UaMV

maicol07 You should catch manually the exception and echo the body to see the full error. This is a Flarum database error

I wasn't able to reproduce – at least with this past test. I'm thinking it may have been that I had a user on my forum that had the same username as the test account with which I was registering on WP. I think I'd earlier deleted from WP, not deleted from Flarum, and tried to re-register. Maybe. ¯_(ツ)_/¯

temey74938

Hey @maicol07,
Can we run it on beta 15? If yes please let me know how.
Thanks.

maicol07

temey74938 yes, you have to use the plugin v2.x. The extension should be automatically installed with the correct version.
Beware: docs are updated to the last version and there isn't any support for d versions. I recommend you to upgrade to beta16 and plugin v3

temey74938

Also can you please explain this step?

You need to create a random token (for security purposes it is better if this is long 40 characters, you can use this tool to make one) and put it into the api_keys table of your Flarum database.

Where and how do I put the API key?

Thanks

askvortsov

temey74938 You'll need to access your database directly and insert it into the API keys table.

tharuka

Hey. I'm new to this whole thing but I faced an issue while implementing SSO. I used the WAMP server for development purposes and I'm getting the following error.

"Fatal error: Uncaught GuzzleHttp\Exception\ConnectException: cURL error 7: Failed to connect to forum.spark.test port 443: Connection refused (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://forum.spark.test/api/users/admin?bySlug=1 in C:\wamp64\www\spark\vendor\guzzlehttp\guzzle\src\Handler\CurlFactory.php on line 210"

maicol07 if you can help me with this that will be great. Verify ssl is also set to false

« Previous Page Next Page »