FriendsOfFlarum OAuth

clarkwinkelmann

streaps thanks, updated! It's indeed compatible with the latest Flarum.

Walys accounts are linked based on email. You can connect with any other social login where you use the same email and you will be logged to the existing account. You can also request a password reset with your email, then you'll be able to connect to that account using a password.

Walys

clarkwinkelmann Perfect.
If I understand you, if the user register via social login all the sign-in need to do it via social login button, if like to login via normal mode with email and password have to request a password reset for the same email registered via social login. Yes?

Ffuser1

Walys yes

Amarok

datitisev oh! Thx. Work again. 🙏

DerFrie

datitisev separate extension can easily hook into this one or Flarum directly and add that.

I will give this kind of implementation a try. Seperating a community owned NC instance from Google etc. makes also sense when considering user experience.

DerFrie

datitisev Maybe have a look at https://github.com/frie/flarum-oauth: IMHO this is just create a Provider class that extends the abstract one in the extension, then hooked into OAuthServiceProvider.php.
My main question: is this possible without creating a fork of the complete extension?
I cannot get the old examples running (tried installing flarum with a version matching the extension version, but after activating one of the auth extensions the admin page does not work any more).

datitisev

DerFrie If I'm understand this correctly, you're asking whether it's possible to add more providers to this extension without forking it? If so, the answer is yes - you just need to tag a class that extends the FoF Oauth Provider class as 'fof-oauth.providers' (see https://github.com/FriendsOfFlarum/oauth/blob/18470619a8aa4c5011348e3305883bb9906f6343/src/OAuthServiceProvider.php#L23-L31).

When you mention old examples, are you referring to previous examples on how to do what I described above? Also, keep in mind Flarum and fof ext versions aren't synced - always installt the latest v1 version for both (1.x.x)

DerFrie

datitisev Referring to this statement:

For a plain example, one can look at the original flarum/auth-twitter extension code.

This extension seems to be bundled with Flarum v0.1.0-beta.13. When installing this version, I find the following line in the log: Package flarum/auth-twitter is abandoned, you should avoid using it. Use fof/oauth instead. When trying to activate the extension anyway, the admin page stops working...

But the option to hook my provider source into fof/oauth without forking this extension is exactly what I was looking for. Just have to figure out the details.

Hari

I have deleted a user called Hari since i have deleted hari could not able log in using social signup. so i wanted to assign an existing account to hari. updated the hari's email id to another account called Mark. after updating hari email id to mark the account he could able to sign in using google login ✔

now i wanted to remove the hari's email id from mark account, updated the mark account's email ID to mark@gmail.com now when hari is trying to log in using login with google he could able to login into marks account.

is this a bug? since hari email id is no longer attached to the account he should not be able to login into mark's account right?

tell me how to clear oauth db? shall i hit uninstall that would fix the issue?

unlink social profile feature is needed to detach the social linking

Hari

clarkwinkelmann

Hari I have deleted a user called Hari since i have deleted hari could not able log in using social signup. so i wanted to assign an existing account to hari. updated the hari's email id to another account called Mark. after updating hari email id to mark the account he could able to sign in using google login ✔

now i wanted to remove the hari's email id from mark account, updated the mark account's email ID to [mark@gmail.com](mailto:mark@gmail.com) now when hari is trying to log in using login with google he could able to login into marks account.

is this a bug? since hari email id is no longer attached to the account he should not be able to login into mark's account right?

--

tell me how to clear oauth db? shall i hit uninstall that would fix the issue?

to fix the issue i am trying to delete oAuth data gut its not getting deleted when i hit uninstall button? how do i manually delete?

Hari

Hari tell me how to clear oauth db? shall i hit uninstall that would fix the issue?

i have tried deleting oAuth data using uninstall but it's not working. how do I manually delete?

edit : i have deleted both profiles issue got resolved

now i am facing issue with Twitter login , i have configured everything correctly, double-checked the credentials but still getting this error

Received HTTP status code [401] with message "{"errors":[{"code":32,"message":"Could not authenticate you."}]}" when getting temporary credentials.

datitisev

DerFrie I see. I was confused on what you were referring to initially, my apologies.

All you need to add your own provider is have a Service Provider that tags your custom provider class (that extends the OAuth abstract provider) with fof-oauth.providers, similar to the linked code. The rest you should be able to ignore, just needing to register the service provider (not to be confused with the provider itself, which is "registered"/tagged in the service provider) in extend.php

DerFrie

datitisev A very helpful hint! I got it up and running productive (also showing up in the extiverse) within few hours, and without changing a line of code in the one main source file. Ended up with a lean implementation, which maybe can serve as a blueprint to satisfy requests for other OAuth providers (as far as provider clients are available). Maybe I will give Mastodon a try later.
By some magic the activation of my supplement on the admin page requires activation of fof/oauth before - makes much sense, and I did nothing to enforce this dependency.

Hari

I am also facing similar issue

Hari now i am facing issue with Twitter login , i have configured everything correctly, double-checked the credentials but still getting this error

Received HTTP status code [401] with message "{"errors":[{"code":32,"message":"Could not authenticate you."}]}" when getting temporary credentials.

Hari

Yes, somone started a dedicated discussion on this.

https://discuss.flarum.org/d/28653-twitter-login-in-fofoauth-shows-401/

Hari

IanM Does it fixes all the login issues with Twitter and Google?

Hari

datitisev

DerFrie Activating your ext requires fof/oauth to be enabled because it's listed in your composer.json dependencies - this was added a few Flarum releases ago, if I remember correctly.

doublethinker

I am having similar issues highlighted above with OAuth via Twitter (I have Github, Google and GitLab working). I have tried Twitter Apps v1.1 and v2.0 to no avail, the api key and secrets are correct (double checked) and callback url is correct as well.

One thing to note is that I am using Cloudflare proxied DNS records.

Here is the log I am receiving:

Next FoF\OAuth\Errors\AuthenticationException: Received HTTP status code [401] with message "{"errors":[{"code":32,"message":"Could not authenticate you."}]}" when getting temporary credentials. in /opt/flarum/vendor/fof/oauth/src/Controllers/TwitterAuthController.php:66Stack trace:
#0 /opt/flarum/vendor/flarum/core/src/Http/RouteHandlerFactory.php(41): FoF\OAuth\Controllers\TwitterAuthController->handle()
#1 /opt/flarum/vendor/flarum/core/src/Http/Middleware/ExecuteRoute.php(27): Flarum\Http\RouteHandlerFactory->Flarum\Http\{closure}()
#2 /opt/flarum/vendor/laminas/laminas-stratigility/src/Next.php(51): Flarum\Http\Middleware\ExecuteRoute->process()
#3 /opt/flarum/vendor/fof/oauth/src/Middleware/ErrorHandler.php(50): Laminas\Stratigility\Next->handle()
#4 /opt/flarum/vendor/laminas/laminas-stratigility/src/Next.php(51): FoF\OAuth\Middleware\ErrorHandler->process()
#5 /opt/flarum/vendor/flarum/core/src/Http/Middleware/ContentTypeOptionsHeader.php(21): Laminas\Stratigility\Next->handle()
#6 /opt/flarum/vendor/laminas/laminas-stratigility/src/Next.php(51): Flarum\Http\Middleware\ContentTypeOptionsHeader->process()
#7 /opt/flarum/vendor/flarum/core/src/Http/Middleware/ReferrerPolicyHeader.php(30): Laminas\Stratigility\Next->handle()
#8 /opt/flarum/vendor/laminas/laminas-stratigility/src/Next.php(51): Flarum\Http\Middleware\ReferrerPolicyHeader->process()
#9 /opt/flarum/vendor/flarum/core/src/Http/Middleware/FlarumPromotionHeader.php(30): Laminas\Stratigility\Next->handle()
#10 /opt/flarum/vendor/laminas/laminas-stratigility/src/Next.php(51): Flarum\Http\Middleware\FlarumPromotionHeader->process()
#11 /opt/flarum/vendor/flarum/core/src/Http/Middleware/ShareErrorsFromSession.php(57): Laminas\Stratigility\Next->handle()
#12 /opt/flarum/vendor/laminas/laminas-stratigility/src/Next.php(51): Flarum\Http\Middleware\ShareErrorsFromSession->process()
#13 /opt/flarum/vendor/flarum/core/src/Http/Middleware/CheckCsrfToken.php(36): Laminas\Stratigility\Next->handle()
#14 /opt/flarum/vendor/laminas/laminas-stratigility/src/Next.php(51): Flarum\Http\Middleware\CheckCsrfToken->process()
#15 /opt/flarum/vendor/flarum/core/src/Http/Middleware/ResolveRoute.php(67): Laminas\Stratigility\Next->handle()
#16 /opt/flarum/vendor/laminas/laminas-stratigility/src/Next.php(51): Flarum\Http\Middleware\ResolveRoute->process()
#17 /opt/flarum/vendor/flarum/core/src/Http/Middleware/SetLocale.php(51): Laminas\Stratigility\Next->handle()
#18 /opt/flarum/vendor/laminas/laminas-stratigility/src/Next.php(51): Flarum\Http\Middleware\SetLocale->process()
#19 /opt/flarum/vendor/flarum/core/src/Http/Middleware/AuthenticateWithSession.php(31): Laminas\Stratigility\Next->handle()
#20 /opt/flarum/vendor/laminas/laminas-stratigility/src/Next.php(51): Flarum\Http\Middleware\AuthenticateWithSession->process()
#21 /opt/flarum/vendor/flarum/core/src/Http/Middleware/RememberFromCookie.php(52): Laminas\Stratigility\Next->handle()
#22 /opt/flarum/vendor/laminas/laminas-stratigility/src/Next.php(51): Flarum\Http\Middleware\RememberFromCookie->process()
#23 /opt/flarum/vendor/flarum/core/src/Http/Middleware/StartSession.php(61): Laminas\Stratigility\Next->handle()
#24 /opt/flarum/vendor/laminas/laminas-stratigility/src/Next.php(51): Flarum\Http\Middleware\StartSession->process()
#25 /opt/flarum/vendor/flarum/core/src/Http/Middleware/CollectGarbage.php(46): Laminas\Stratigility\Next->handle()
#26 /opt/flarum/vendor/laminas/laminas-stratigility/src/Next.php(51): Flarum\Http\Middleware\CollectGarbage->process()
#27 /opt/flarum/vendor/flarum/core/src/Http/Middleware/ParseJsonBody.php(28): Laminas\Stratigility\Next->handle()
#28 /opt/flarum/vendor/laminas/laminas-stratigility/src/Next.php(51): Flarum\Http\Middleware\ParseJsonBody->process()
#29 /opt/flarum/vendor/flarum/core/src/Http/Middleware/HandleErrors.php(57): Laminas\Stratigility\Next->handle()
#30 /opt/flarum/vendor/laminas/laminas-stratigility/src/Next.php(51): Flarum\Http\Middleware\HandleErrors->process()
#31 /opt/flarum/vendor/flarum/core/src/Http/Middleware/InjectActorReference.php(25): Laminas\Stratigility\Next->handle()
#32 /opt/flarum/vendor/laminas/laminas-stratigility/src/Next.php(51): Flarum\Http\Middleware\InjectActorReference->process()
#33 /opt/flarum/vendor/laminas/laminas-stratigility/src/MiddlewarePipe.php(76): Laminas\Stratigility\Next->handle()
#34 /opt/flarum/vendor/middlewares/request-handler/src/RequestHandler.php(84): Laminas\Stratigility\MiddlewarePipe->process()
#35 /opt/flarum/vendor/laminas/laminas-stratigility/src/Next.php(51): Middlewares\RequestHandler->process()
#36 /opt/flarum/vendor/middlewares/base-path-router/src/BasePathRouter.php(101): Laminas\Stratigility\Next->handle()
#37 /opt/flarum/vendor/laminas/laminas-stratigility/src/Next.php(51): Middlewares\BasePathRouter->process()
#38 /opt/flarum/vendor/laminas/laminas-stratigility/src/Middleware/OriginalMessages.php(36): Laminas\Stratigility\Next->handle()
#39 /opt/flarum/vendor/laminas/laminas-stratigility/src/Next.php(51): Laminas\Stratigility\Middleware\OriginalMessages->process()
#40 /opt/flarum/vendor/middlewares/base-path/src/BasePath.php(73): Laminas\Stratigility\Next->handle()
#41 /opt/flarum/vendor/laminas/laminas-stratigility/src/Next.php(51): Middlewares\BasePath->process()
#42 /opt/flarum/vendor/flarum/core/src/Http/Middleware/ProcessIp.php(24): Laminas\Stratigility\Next->handle()
#43 /opt/flarum/vendor/laminas/laminas-stratigility/src/Next.php(51): Flarum\Http\Middleware\ProcessIp->process()
#44 /opt/flarum/vendor/laminas/laminas-stratigility/src/MiddlewarePipe.php(76): Laminas\Stratigility\Next->handle()
#45 /opt/flarum/vendor/laminas/laminas-stratigility/src/MiddlewarePipe.php(65): Laminas\Stratigility\MiddlewarePipe->process()
#46 /opt/flarum/vendor/laminas/laminas-httphandlerrunner/src/RequestHandlerRunner.php(96): Laminas\Stratigility\MiddlewarePipe->handle()
#47 /opt/flarum/vendor/flarum/core/src/Http/Server.php(44): Laminas\HttpHandlerRunner\RequestHandlerRunner->run()
#48 /opt/flarum/public/index.php(26): Flarum\Http\Server->listen()
#49 {main}

clarkwinkelmann

doublethinker have you provided Twitter with your terms of use URL? Did you request access to the user email? I believe those two options are necessary before login is possible.

doublethinker

clarkwinkelmann

Yes I have to all points- although the terms of use and privacy pages are sparse at the moment. I'm not of the impression that they are important to enable functionality?

clarkwinkelmann

doublethinker last time I tried it was just a matter of providing any URL, and then it worked. Maybe there's a review process nowadays?

It's been a little while since I tried to configure Twitter so I'm not sure what it could be, and not sure how we can get additional details about the error.

doublethinker

clarkwinkelmann There was a review process for the developer account but it's since been activated.

Yeah I'm at a loss too, seems like a big mysterious issue over at twitter dev forums: https://twittercommunity.com/tag/error-32

JonAtleSandbakken

Same problem here. I got all the social logins to work, except Twitter, with the following error: Received HTTP status code [401] with message "{"errors":[{"code":32,"message":"Could not authenticate you."}]}" when getting temporary credentials.

Hari

Ffuser1 what's your website address?

Not possible to disclose

Ffuser1 It's possible you're being blocked from accessing the Api if your terms and privacy policy is not visible in your home page.

If it's the case, you'll have to make sure those conditions are met then you reapply (in your application make it clear that it's only email, and profile picture you will use and that it's

I'm pretty sure that's not the case

Ffuser1 Also, recheck key and token.

That's the first thing I did, I'm sure everything is correctly configured.

Maybe this issue only happening with sub directories? Or cloudflare's firewall settings?

JonAtleSandbakken guswogjs499

3 of us having the same issue

Could you please confirm that both of you running flarum in a sub directory?

« Previous Page Next Page »