Topic-icon Google authorization stopped working

Active Subscriptions:

None
5 years 5 months ago - 5 years 5 months ago #64776 by lukasz.pasula
Hi,

For the recent few hours we can see that the plugin does not work for Google authorization. Has anything changed with the Google logging in process? We had not changed anything with our Joomla website recently.

Update:
Many our users use Google accounts for logging in but it seems that they lost this possibility today.

So far I tried many different solutions I could imagine, including upgrading the JFBConnect plugin and checking settings both in Google API project and Joomla / plugin.
After all didn't work, I created a new app (project) in Google according to this tutorial (btw it needs some update): www.sourcecoast.com/jfbconnect/docs/soci...le-application-setup
But it changed nothing.

The effect is still the same:
when clicking on the Google+ button on my Joomla website, it first redirects me to the google page, next it requires from me choosing my Google account (assuming I didn't do this before), and after several seconds I'm redirected again to... Joomla login page, like nothing happened. Clicking again on the Google+ login button (provided by the plugin) brings the same result: at the end I'm redirected to Joomla login page on my website.

I was checking the Debug console - what I've got for Google+ is this:

"com_jfbconnect": {
"login": {
"return": null
}
}

I.e. null value.
Interestingly, for Facebook it works well, and we get normal data when users tries to log in through their facebook accounts.

I also tried to make some further debugging, and I can see that there is the possibility to enable the "Debug Mode" option in the JFBConnect configuration page. So I enabled it for both "Logging only" and fully enabled settings. But the logging system in the pluging seems to log not much... For example, we get no entries about people logging in (for facebook they should work, as stated above), and even about error login trials.
The question is: what information the jfbconnect.log file is supposed to store?
Last edit: 5 years 5 months ago by lukasz.pasula.
The topic has been locked.
Active Subscriptions:

None
5 years 5 months ago #64778 by crommie
Looks like I have the same problem, only with one user on one of my sites. I remember something with OpenID and Google +, could it be related to this? I noticed every other user on my site has a Google+ account.
This user is relatively new, maybe he doesn't have a Google + account (yet)?

SourceCoast-Alex? Any thoughts on this?
The topic has been locked.
Support Specialist
5 years 5 months ago #64781 by alzander
We're unsure why you're having issues with Google authentication. There haven't been any announcements from Google about changes that would break authentication. The latest release of JFBConnect, v8.0, had some updates for Google Authentication based on changes they made to the Google+ platform. We have tested Google+ on this site (please do so yourself) as well as some development sites and can't recreate the issue.

With that said, I believe you're having issues, but I just don't have an answer immediately.

The Debug setting in JFBConnect has options for Yes/No/Log Only. Please set it to 'Yes'. That should show any error messages that may be occurring on the front-end during authentication.

If no messages are shown, please:
* Disable any caching you have enabled - Global Configuration or separate plugins
* Disable SEF URLs in Joomla or any 3rd party extensions

If that still fails, please let us know a site where we can test and we'll gladly investigate further.

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
5 years 5 months ago #64784 by crommie
Okay I know I'm hijacking someone else's topic here (sorry Lukasz!), but my problem is solved.

Summary: this particular user's Google account had been shut down. After a while, my client opened a new Google account for the user, but inbetween JFBConnect had noticed that the Google account no longer existed. Some way JFBConnect couldn't connect his new Google account to the existing Joomla user.

Solution: I altered his existing account and created a new one using JFBConnect. The user was able to login again!

New problem: All the actions connected to this user had to stay intact and they could only be connected to this one user, so I had to merge both accounts. I did this by swapping the IDs. And, you may have guessed: user was no longer able to login.

Solution: I dug a little deeper and looked at the user information in the JFB User map. Two accounts, one with and one without social profile. I headed for the JFB User map table in the database. Swapping the IDs in there as well did the trick.

User happy, client happy, I'm happy.
The topic has been locked.
Support Specialist
5 years 5 months ago #64785 by alzander
It's not hijacking because it was potentially related. I'm glad you got things resolved. There can be a little confusion and issues when a user wants to switch the connected social network account they want to use with their existing Joomla account. There are some front-end tools to let the user do this as well, like the JFBConnect -> Account Settings menu item, where the can see, re-link and un-link social networks to their Joomla account. That's much better than having to manually tinker with the database.

It's also helpful as it means the original issue is likely not a systemic problem affecting many sites with JFBConnect.

lukasz.pasula,
If there's any more details you can share on what's happening on your site, if it's specific users or any other information, that would really help us determine the proper course of action.

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
5 years 5 months ago #64787 by lukasz.pasula
Alex,

All caching is disabled. SEF is disabled. Debug Mode in JFBConnect configuration is On. We can see in the log a message: Settings updated! No errors, warnings or any other info during sing in attempts.

All users can sign in / sign up with FB, no users can sign in / sign up with G+ (although it was possible 4 days ago an no changes were made by us).

We updated JFBConnect to the newest version 8.0.3 and created new G+ API credentials (on two separated Google accounts) and tested it. Unfortunately, it did not help.

I'll send you links and other data in a private message.

Regards
Lukasz
The topic has been locked.
Support Specialist
5 years 5 months ago #64788 by alzander
Lukasz,
Thanks for the info on your site. We were able to test and definitely can see there is a problem. However, from the access we have, I can't make heads or tails of what's going wrong. We'll need to add some debug code to the authentication process to see where things are getting hung up.

Can you send FTP credentials as well? With that, we can dig right in and get you fixed up.

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
5 years 5 months ago #64790 by lukasz.pasula
Alex, is there any progress on the issue?

Regards,
Lukasz
The topic has been locked.
Support Specialist
5 years 5 months ago #64795 by alzander
Lukasz,
Sorry for not getting to this yesterday. I was just able to FTP in and try to add some debug code. However, no changes I apply in the files are actually occurring on the site. This could mean that I'm in the wrong directory, but I don't think that's the case. More likely, what it means is that there's some sort of PHP caching that's happening on your site that isn't updating when files are changed. PHP caching (also called Opcaching) will read a PHP file one time, compile it and then not read that file anymore unless it's been changed. That's great for performance. There are times though when the OpCache can be tuned to not check for updates of PHP files at all and only clear the cache (reload the files) when instructed to do so.

My belief for what happened is that you upgraded JFBConnect at some point, but all of the files that JFBConnect updated were not properly reloaded. That's preventing some of the new code we have for Google authentication from working.

One quick demonstration and method to test is that I updated the phpinfo.php file in your root directory. That file was already there and simply ran "phpinfo();" which shows your php configuration. I edited the file and added:
echo "PHP INFO. SourceCoast Test";
If you load that file (yoursite.com/phpinfo.php) that new test is not showing on the page like it should. That means it's not a Joomla issue at all, but something higher level with the server configuration that is not allowing changes to PHP to take effect.

I hope that helps investigate, but if you need anything else or further investigation, please don't hesitate to get in touch.

Finally, I'd recommend removing the phpinfo.php, kickstart.php and any other php scripts on your site that are publicly accessible. Those expose information about your site or allow execution of scripts and code that you don't want anyone to your site to be able to run.

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
5 years 5 months ago #64797 by lukasz.pasula
Alex, we do have OPCache installed but the files are updated after every change. I can see the changes you made to phpinfo file, thus I would like you to check again.

We moved around 2 months ago to a new VPS server and did not upgrade JFBConnect since then (except development environment after the break of G+ authentication). Although server configuration could be the problem I don't think that's the case or at least there are not enough reasons to claim that.

Yes, we are aware that files like phpinfo shouldn't be available publicly but this is our development environment and I made it public only for your support. Honestly, I hoped it won't take more than a day or two. Now it's over a week. This is a real problem for our users because people that registered with G+ are having trouble to log in to their accounts and use the service they paid for. (Yes, we are giving instructions how to log in by email, but people in a rush don't read a lot.)

Alex, please take this seriously or just say straight you will not support us on this issue. We need to resolve that fast and if you can't help us then we will drop the plugin and make a workaround on our own. This is not the support I hoped for.

Regards,
Lukasz
The topic has been locked.