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

tharuka

Hi @maicol07
Sorry to bother you a lot.
My folder structure is like this

www
->sso
-->forum
------>public
------>vendor
-->vendor
-->index.php
-->flarum.php
-->delete.php
->.......

index.php for login in inside the sso folder and forum folder is also at the same place
localhost/sso to load login page and localhost/sso/forum/public is the forum url.

I used these parameters as follows
FLARUM_HOST=http://localhost/sso/forum/public
API_KEY=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
ROOT_DOMAIN=localhost

Can you point out anything wrong with this configuration? I used the given example login forms with your php library. Still I can't figure out this problem. It always redirects me to localhost intsed of forum public url which I redirected using header("Location: http://localhost/sso/forum/public"); after logging in

maicol07

tharuka do you get logged into Flarum if you return to it manually?

tharuka

maicol07 Yes. After getting redirected to localhost I can go to localhost/sso/forum/public folder and I'm logged in.

maicol07

tharuka are you able to check if it gets redirected before the login middleware by echoing something?

tharuka

maicol07 When I echo Done at LoginMiddleware I get an output like below

Done
( ! ) Fatal error: Uncaught Laminas\HttpHandlerRunner\Exception\EmitterException: Output has been emitted previously; cannot emit response in C:\wamp64\www\sso\forum\vendor\laminas\laminas-httphandlerrunner\src\Exception\EmitterException.php on line 24
( ! ) Laminas\HttpHandlerRunner\Exception\EmitterException: Output has been emitted previously; cannot emit response in C:\wamp64\www\sso\forum\vendor\laminas\laminas-httphandlerrunner\src\Exception\EmitterException.php on line 24
Call Stack

Time Memory Function Location

1 0.0001 363392 {main}( ) ...\index.php:0
2 0.0027 387304 Flarum\Http\Server->listen( ) ...\index.php:26
3 0.0822 3048680 Laminas\HttpHandlerRunner\RequestHandlerRunner->run( ) ...\Server.php:44
4 0.1072 3877880 Laminas\HttpHandlerRunner\Emitter\SapiEmitter->emit( ) ...\RequestHandlerRunner.php:98
5 0.1072 3877880 Laminas\HttpHandlerRunner\Emitter\SapiEmitter->assertNoPreviousOutput( ) ...\SapiEmitter.php:27

this line 24 is the echo line which I put. It is getting redirected at the LoginMiddleware. This only happens when a user logged in for the first time after logging out.

maicol07

tharuka ok, what you need to see is the done. Check if the issue occurswhen login middleware redirects. Also try to dump this: echo (string) $request->getUrl();

Don't worry about the other errors, they are only related to the forced output you echo

tharuka

maicol07 this dumps http://localhost/ as the echo output and after login in always it redirects to localhost root in login middleware in this return return new RedirectResponse($request->getUri()).

So sorry about wasting your valuable time.

maicol07

tharuka Still I can't reproduce the issue on my local environment. Can you test it in production or on a staging copy or clone of the production Flarum (on the same server)? Maybe it's only something related to localhost (I always use custom domains for development and local environment since it's like testing in a production enviroment)

drivencompassion

What about the reverse, flarum on root and various separate wp installs on different subfolders?

maicol07

drivencompassion That's not possible with this extension. This feature should be a separate extension, I think. It wouldn't be useful to the majority of the people using this extension

tharuka

maicol07 I tested it in my server with my domain as well.. same result..

drivencompassion

maicol07 https://discuss.flarum.org/d/27303-flarum-on-root-wordpress-on-subdomain-folders

maicol07

tharuka it seems there is a new fix for your issue that will be available in the next update: https://tracker.maicol07.it/issue/FSSOE-19

maicol07

Release time!

Flarum extension - 1.10

Released on May 22, 2021

✨ Features

eda72a0 5485b84 5e58a02 ✨ Compatibility with Flarum 1.0

PHP Plugin - 3.0.1

Released on May 22, 2021

🐛 Bug Fixes

0dd2465 🐛 Groups created even if they already exists in Flarum

Other changes

f3c9c50 🔥 Removed set_groups_admins as no more used

Implementation of this should be made by the user

WP Plugin 2.2

Updated in the WP repo (should be up within minutes)
✨ Automatic composer installer
✨ Added option to toggle avatars auto sync
🐛 Return a previously triggered error during login
🐛 Use SSL cert path when trying to verify SSL
🐛 Fixed user image always set to gravatar default

As always, check the docs to know how to update to the latest version!

Hari

maicol07 Yay 🎉

did you update at wordpress store too ?

https://wordpress.org/plugins/sso-flarum/

shall i run a fresh installation in my local host ? hope i can try now

maicol07

Hari

maicol07 Updated in the WP repo (should be up within minutes)

Yes, I'm uploading it now

Hari

Hari Last updated:4 mins ago 👍

maicol07

I'm investigating an issue that raises an exception about the WP repo version of the WP plugin. In the meantime, don't update to 2.2!

maicol07

2.2.1 should be out now with fixes. Update to this new version (either from WP dashboard or manually from Github release zip). Feedbacks are welcome!

Hari

i've installed laragon and trying, i have around 15k user database at main website i dont want to back up and try . so trying locally . i badly want to switch to sso but i could not install .. i'm trying .. if possible could you assist

PS R:\laragon\www\flarum> composer require maicol07/flarum-ext-sso
Using version ^1.10 for maicol07/flarum-ext-sso
./composer.json has been updated
Running composer update maicol07/flarum-ext-sso
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires maicol07/flarum-ext-sso ^1.10 -> satisfiable by maicol07/flarum-ext-sso[1.10].
    - maicol07/flarum-ext-sso 1.10 requires flarum/core ^1 -> found flarum/core[dev-master, 1.x-dev (alias of dev-master)] but it does not match your minimum-stability.

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

i want my users to change their DP at flarum only .. if they change at wordpress i do not want that to reflect in flarum .. is that possible ?

maicol07

Hari 2.2.1 is the new WP plugin release, not the extension 😅
The extension has been updated to 1.10 yesterday but it is compatible with Flarum 1.0 only. However, there are no changes other than compatibility, so 1.9 works fine with beta16.
Try fixing the version in composer.json

Plugins (last two versions) are compatible with 1.9 and 1.10.

Hari

maicol07 yay it worked 🌼

Edited

Hari i want my users to change their DP at flarum only .. if they change at wordpress i do not want that to reflect in flarum .. is that possible ?

is it possible ? or profile pic will sync automatically ? i dont want it to be synced

Hari

maicol07 😢 i was searching everywhere regarding the errors 😅😅😅

what was that cmd line to install specific version only ? let me know for beta 16

it will be something like composer require maicol07/flarum-ext-sso vers1.00 idk i forgot

« Previous Page Next Page »