Yahoo & VK Logins not working

I have followed the steps for setting up Yahoo Login and the button shows up but clicking this just results in a 504 Timeout error. Are there additional steps to be taken for this to work? Facebook, twitter and google all work fine. I notice there is something on the yahoo site saying a project needs to be created but not sure if or how relevant that is.

With VK, the VK site shows a message stating that the app needs access etc but when you click "Allow" there is no further response until the whole thing times out. Again, there is a field in the VK setup about a callback URL that does not appear in the setup instructions so not quite sure what to put there since it does not accept the format of other callback urls as these have parameters and the VK setup does not accept any parameters.

Sent.

As per my PM, it appears the issues I am facing is not on the provider's end but with any provider with a callback to "/index.php?option=com_jfbconnect&task=authenticate.callback". Only Twitter does not make such a call and is the only reliable one working for me.

Thanks for getting back.

Can you help me by telling me which function in the component handles this call: /index.php?option=com_jfbconnect&task=authenticate.callback&provider=vk&code=abc&state=xyz.

It doesn't seem to be the callback function in /components/com_jfbconnect/controllers/authenticate.php as i would have thought.

This will help me start debugging in an effort to determine where the slowdown is exactly happening.

Thanks

Hi,

I added debug flags, die("message"), which were not triggered but I later found out this was with Facebook which does not use that callback function.

Okay, I am now only focussing on 3 providers: Twitter, Facebook and Google.

The status of each is as follows.

Twitter: No Issues at all.
Facebook: Ultimately works but very slow. Takes about 30 seconds to complete.
Google: 504 Timeout error 99 times out of 100.

Facebook does not use the callback function and leaving this aside for now.

Twitter does use this function but works perfectly well. Google, and presumably, Yahoo, VK etc, all use this but invariably timeout.
The delay experienced with the others only happen AFTER this callback function is called.

So, if when i add a 'die("message")' flag to the beginning of the callback function and click the button, it is hit immediately for Twitter, Google, Yahoo, VK etc. So the issue is not the provider authenticating and returning to my site but with what happens afterwards while running the callback function for the other providers apart from Twitter.

By moving the "die" flag down the function code, I have found that the delay kicks in while running "$provider->client->authenticate();".
Tracking through the code led me to the authenticate function in "/components/com_jfbconnect/libraries/authentication/oauth2base.php"

A "die" flag at the beginning of that function is called immediately, so no delays up to calling that function and the delay comes in around Line 87 when running "$response = $this->http->post($this->getOption('tokenurl'), $data);"

A look at the developer console shows that a GET request of the form:

"accounts.google.com/o/oauth2/auth?respon...approval_prompt=auto"

The delay seems to happen in waiting for a response to this call.

Actually, when I make that request directly into my browser I end up waiting forever. (I know this can't handle it perhaps, but expect some immediate error to show that the provider has received and perhaps rejected the browser call).

Wonder whether you can give me some insights on what to further look into given this information.
The interesting thing is why this doesn't affect Twitter given that it runs through the same functions. Facebook is clear as it uses a different approach. Is there something to change with the affected providers to make them consistent with Twitter's outcome?

Hi Alex,

Thanks for taking a look. I also get an instant 400 error with the posted url and I believe this is because the url is invomplete and the "client_id=12345.mypublickey" and "www.example.com" parameters are not "real" values. I will PM you a "real" version if you don't mind.