Topic-icon Windows LIve EasySocial Signup Not Working

Active Subscriptions:

None
11 years 8 months ago #47368 by davpar
Hi.
Just upgraded to 6.2. Have configured the Windows Live settings as suggested, but when trying to sign up with WL I get the error message:
We were unable to retrieve your WindowsLive account information. Please try again.

Running latest ES (1.3.6) and Joomla 3.3.4

Dave
The topic has been locked.
Support Specialist
11 years 8 months ago #47373 by alzander
To remove EasySocial from the equation, can you:
* Disable any Social Profile plugins you have enabled
* Set the "Registration Component" setting in JFBConnect to "JFBConnect"

Also, please:
* Disable SEF URLs
* Disable Caching
* Set the "Enable Debug Mode" setting to "Yes" in the JFBConnect configuration area.

That should narrow things down quite a bit as to whether it's a configuration, JFBConnect, or integration issue with EasySocial. From there, we should be able to help determine the best solution.

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

None
I have this problem and when in debug mode it gives me the error of...

Error
SSL certificate problem: unable to get local issuer certificate.
The topic has been locked.
Support Specialist
11 years 8 months ago #47424 by alzander
Giancarlo,
If you're seeing that message, it means the SSL root certificates are not up to date on your server. Without those certificates, your site is unable to validate the WindowsLive servers as authentic and the secure request is being denied. You'll need to contact your hosting provider to get the SSL certificates updated so that the following URL can be validated:
login.live.com/

I hope that helps get you going, but if you continue to run into issues, just let me know, and we'll gladly help however we can.

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

None

alzander wrote: Giancarlo,
If you're seeing that message, it means the SSL root certificates are not up to date on your server. Without those certificates, your site is unable to validate the WindowsLive servers as authentic and the secure request is being denied. You'll need to contact your hosting provider to get the SSL certificates updated so that the following URL can be validated:
login.live.com/

I hope that helps get you going, but if you continue to run into issues, just let me know, and we'll gladly help however we can.

Thanks,
Alex


Thanks Alex, I went back to siteground with this information and double checked but my SSL Certificate is all up to date and there is NO problems with it, so I am at a loss as to what to do and siteground cannot go any further with it?
The topic has been locked.
Support Specialist
11 years 8 months ago #47435 by alzander
It's not *your* SSL certificate that needs to be validated. It's the SSL certificate from the login.live.com address that needs to be validated by your server. The message above indicates that your server is unable to validate *the Microsoft* SSL certificate.

From a command prompt, try running the following command:
curl https://login.live.com/ -v
My guess is that you'll see something like:
SSL certificate problem, verify that the CA cert is OK. Details:
That's not going through the full PHP stack, so even if that works, it's not a guarantee it will work in PHP/Joomla. If that doesn't work though, it's a great indicator of the cause.

I hope that helps,
Alex
The topic has been locked.
Active Subscriptions:

None
11 years 8 months ago - 11 years 8 months ago #47464 by Giancarlo.Massironi

alzander wrote: It's not *your* SSL certificate that needs to be validated. It's the SSL certificate from the login.live.com address that needs to be validated by your server. The message above indicates that your server is unable to validate *the Microsoft* SSL certificate.

From a command prompt, try running the following command:

curl https://login.live.com/ -v
My guess is that you'll see something like:
SSL certificate problem, verify that the CA cert is OK. Details:
That's not going through the full PHP stack, so even if that works, it's not a guarantee it will work in PHP/Joomla. If that doesn't work though, it's a great indicator of the cause.

I hope that helps,
Alex


Thanks Alex, Siteground ran the tests and came back to me with this
Code:
curl https://login.live.com/ -v 
* About to connect() to login.live.com port 443 (#0) 
* Trying 131.253.61.68... 
* Adding handle: conn: 0x1a92db0 
* Adding handle: send: 0 
* Adding handle: recv: 0 
* Curl_addHandleToPipeline: length: 1 
* - Conn 0 (0x1a92db0) send_pipe: 1, recv_pipe: 0 
* Connected to login.live.com (131.253.61.68) port 443 (#0) 
* successfully set certificate verify locations: 
* CAfile: /etc/pki/tls/certs/ca-bundle.crt 
CApath: none 
* SSLv3, TLS handshake, Client hello (1): 
* SSLv3, TLS handshake, Server hello (2): 
* SSLv3, TLS handshake, CERT (11): 
* SSLv3, TLS handshake, Server key exchange (12): 
* SSLv3, TLS handshake, Server finished (14): 
* SSLv3, TLS handshake, Client key exchange (16): 
* SSLv3, TLS change cipher, Client hello (1): 
* SSLv3, TLS handshake, Finished (20): 
* SSLv3, TLS change cipher, Client hello (1): 
* SSLv3, TLS handshake, Finished (20): 
* SSL connection using ECDHE-RSA-AES256-SHA384 
* Server certificate: 
* subject: 1.3.6.1.4.1.311.60.2.1.3=US; 1.3.6.1.4.1.311.60.2.1.2=Washington; businessCategory=Private Organization; serialNumber=600413485; C=US; postalCode=98052; ST=Washington; L=Redmond; street=1 Microsoft Way; O=Microsoft Corporation; OU=MSA; CN=login.live.com 
* start date: 2013-10-23 00:00:00 GMT 
* expire date: 2014-10-23 23:59:59 GMT
* subjectAltName: login.live.com matched
* issuer: C=US; O=VeriSign, Inc.; OU=VeriSign Trust Network; OU=Terms of use at https://www.verisign.com/rpa (c)06; CN=VeriSign Class 3 Extended Validation SSL SGC CA
* SSL certificate verify ok.
> GET / HTTP/1.1
> User-Agent: curl/7.30.0
> Host: login.live.com
> Accept: */*
Last edit: 11 years 8 months ago by Giancarlo.Massironi.
The topic has been locked.
Active Subscriptions:

None
11 years 8 months ago #47466 by davpar
Hi all.
I also asked my provider to check the SSL status. They have confirmed that there is no problem reading the Microsoft SSL:
==============
curl login.live.com/ -v
* About to connect() to login.live.com port 443 (#0)
* Trying 131.253.61.66... connected
* Connected to login.live.com (131.253.61.66) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* SSL connection using TLS_RSA_WITH_AES_256_CBC_SHA
* Server certificate:
* subject: CN=login.live.com,OU=MSA,O=Microsoft Corporation,STREET=1 Microsoft Way,L=Redmond,ST=Washington,postalCode=98052,C=US,serialNumber=600413485,businessCategory=Private Organization,incorporationState=Washington,incorporationCountry=US
* start date: Oct 23 00:00:00 2013 GMT
* expire date: Oct 23 23:59:59 2014 GMT
* common name: login.live.com
* issuer: CN=VeriSign Class 3 Extended Validation SSL SGC CA,OU=Terms of use at www.verisign.com/rpa (c)06,OU=VeriSign Trust Network,O="VeriSign, Inc.",C=US
> GET / HTTP/1.1
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.15.3 zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> Host: login.live.com
> Accept: */*
==============================
Dave
The topic has been locked.
Support Specialist
11 years 8 months ago #47476 by alzander
There's 2 different questions above, which I didn't realize there were different errors for. It's possible the issues are related, but not sure.

First, Giancarlo, are you using EasySocial as well? If not, please start a new topic for your issue. While you're having WindowsLive authentication issues, I'm not sure it's related to Dave's problem, which seems a little more generic.

To further check the SSL issue, if that's the underlying problem you're both having, can you create the following file on your site and run it:
Filename: curl_test.php
Contents:
<?php
$url = 'https://login.live.com/';
$opts[CURLOPT_URL] = $url;
$opts[CURLOPT_SSL_VERIFYPEER] = true;
$opts[CURLOPT_VERBOSE] = true;
$opts[CURLOPT_RETURNTRANSFER] = 1;

$ch = curl_init();
curl_setopt_array($ch, $opts);
$result = curl_exec($ch);

$errno = curl_errno($ch);
echo "Error Number: " . $errno . "\n";
When you run that, it should have output similar to:

* About to connect() to login.live.com port 443 (#0)
* Trying 131.253.61.80...
* Adding handle: conn: 0x10280b800
* Adding handle: send: 0
* Adding handle: recv: 0
* Curl_addHandleToPipeline: length: 1
* - Conn 0 (0x10280b800) send_pipe: 1, recv_pipe: 0
* Connected to login.live.com (131.253.61.80) port 443 (#0)
* successfully set certificate verify locations:
* CAfile: /Applications/XAMPP/xamppfiles/share/curl/curl-ca-bundle.crt
CApath: none
* SSL connection using ECDHE-RSA-AES256-SHA384
* Server certificate:
* subject: 1.3.6.1.4.1.311.60.2.1.3=US; 1.3.6.1.4.1.311.60.2.1.2=Washington; businessCategory=Private Organization; serialNumber=600413485; C=US; postalCode=98052; ST=Washington; L=Redmond; street=1 Microsoft Way; O=Microsoft Corporation; OU=MSA; CN=login.live.com
* start date: 2013-10-23 00:00:00 GMT
* expire date: 2014-10-23 23:59:59 GMT
* subjectAltName: login.live.com matched
* issuer: C=US; O=VeriSign, Inc.; OU=VeriSign Trust Network; OU=Terms of use at www.verisign.com/rpa (c)06; CN=VeriSign Class 3 Extended Validation SSL SGC CA
* SSL certificate verify ok.
> GET / HTTP/1.1
Host: login.live.com
Accept: */*
.....
Error Number: 0

That will take Joomla out of the equation, but will run the test using PHP's cURL configuration, which may different than the command line version.

Please let me know how that goes. If it passes, please Private Message me admin and FTP credentials to your site and we'll investigate further. If it fails, it means the PHP configuration of your site is not using the latest SSL credentials that exist and work from the command prompt.

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

None
11 years 8 months ago #47477 by davpar
Hi.
The only response I got on the screen was Error Number: 0
I didn't get any of the other output (although don't know if you missed some of the code out, as I had to put in the closing ?> tag.
Dave
The topic has been locked.