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

peppogiappe

maicol07

peppogiappe Check if this helps: https://discuss.flarum.org/d/20867-csrf-token-mismatch-on-beta-9-upgrade/

peppogiappe

maicol07 Sometimes i get also 405 method not allowed

peppogiappe

maicol07 Is it a problem if I'am in local environment? my url to flarum is a virtual host: http://flarum.local.. the root domain is local or flarum.local?

maicol07

peppogiappe Maybe, I'm actually testing next version with XAMPP. Flarum is a subdomain or a domain (and local is the extension) in your url?

peppogiappe

maicol07 yes, i'am using localhost to hit the index.php of sample-website inside the extension, and flarum.local is the forum, but always under localhost, only with a virtual host

peppogiappe

maicol07 I have also read that maybe there is a problem with password that i pass to login? I'am passing to login password not hashed

maicol07

peppogiappe what is your root domain?

maicol07

peppogiappe Yeah, must be a plain password only if user was signed up before the SSO extension was enabled

peppogiappe

maicol07 local i think

peppogiappe

maicol07 i am trying without enable the extension.. because the extension only redirect users true?

maicol07

peppogiappe Well, it also activates the user

peppogiappe There should be no problem then...

peppogiappe

maicol07 Activates new users, but not if them are already in the database before the extension activated true?

maicol07

peppogiappe Exactly

peppogiappe

maicol07 So can i go on trying with your extension inside my localhost and my forum under a virtual host?

maicol07

peppogiappe I don't know if that will work. You have to test it.

peppogiappe

maicol07 I noticed that there is a bug calling /api/token flarum/core2095

maicol07

peppogiappe Follow @luceos instructions in your thread

maicol07

Before I start with the changelog of this great version, I want to say that this should have been version 2.0, but I decided to separate the Flarum extension and the plugins. So now there are 3 changelogs and plugins versions start from 1.0:

Release 1.5 (Extension)

Changelog

Moved website plugin to its own repo

Updating

Run composer update command or use Bazaar

Release 1.0 (PHP Plugin)

Changelog

BREAKING CHANGE! PHP 7+ required
BREAKING CHANGE! New request system: now using the great Flagrow API client
New Cookie management: now using the awesome Cookie library by Delight-im
New option: insecure mode (principally for local development, read in docs for more)
Added groups settings for users: you can now set a group for a user and, if doesn't exists, it will be created!
BREAKING CHANGE! Deleted sendRequest and get methods as no more used.
Code and performance improvements
Various fixes (see also the bug tracker)

Installing

Read the new Docs

Release 1.0 (WP Plugin)

Changelog

All the new features in PHP plugin
New settings page
Paid PRO features (read more on Docs, link below)
Memberpress plugin integration (PRO FEATURE)
Published to the WordPress Plugin Directory! [WAITING APPROVAL]

Installing

Read the new Docs

Links

Github
Docs

Nimren

Successfully installed and adjusted but does not work.
When i open directly /wp-login.php it shows me an error: Error: Invalid username, email address or incorrect password.
When I try to log in via flarum it shows me this error:

Fatal error: Uncaught GuzzleHttp\Exception\ClientException: Client error:POST https://myfarum.site.com/api/tokenresulted in a401 Unauthorizedresponse: {"errors":[{"status":"401","code":"not_authenticated"}]} in /home/mysite/public_html/wp-content/plugins/flarum-sso-extension/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:113 Stack trace: #0 /home/mysite/public_html/wp-content/plugins/flarum-sso-extension/vendor/guzzlehttp/guzzle/src/Middleware.php(65): GuzzleHttp\Exception\RequestException::create(Object(GuzzleHttp\Psr7\Request), Object(GuzzleHttp\Psr7\Response)) #1 /home/mysite/public_html/wp-content/plugins/flarum-sso-extension/vendor/guzzlehttp/promises/src/Promise.php(203): GuzzleHttp\Middleware::GuzzleHttp\{closure}(Object(GuzzleHttp\Psr7\Response)) #2 /home/mysite/public_html/wp-content/plugins/flarum-sso-extension/vendor/guzzlehttp/promises/src/Promise.php(156): GuzzleHttp\Promise\Promise::callHandler(1, Object(GuzzleHttp\Psr7\Response), Array) #3 /home/mysite/public_html/wp- in /home/mysite/public_html/wp-content/plugins/flarum-sso-extension/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php on line 113

maicol07

Nimren have you set the Flarum URL in settings?

peppogiappe

Nimren Go inside /vendor/flarum/core/src/Http/Middleware ... something like this, and search the class named CheckCsrfToken (almost) and edit a method for now, waiting for Flarum beta 13: you have to edit in this way

if ($request->getAttribute('bypassCsrfToken', true)) { return $handler->handle($request); }

« Previous Page Next Page »