After performing a system update, Empathy is unable to login to AIM and ICQ. Interestingly, Pidgin is also experiencing the same error, reporting the problem as "Received unexpected response from https://api.screenname.aol.com/auth/clientLogin". Empathy didn't specify what the problem was.
On the basis of that error, I ran Wireshark and watched the login attempt.
Empathy sends the following request to the server (with personal details omitted):
<?xml version="1.0" encoding="UTF-8"?>
<response xmlns="http://developer.aim.com/xsd/aim.xsd"><statusCode>400</statusCode><statusText>useTLS=1 is not allowed for non secure requests.</statusText><data><ts>1263348414</ts><upgradeData></upgradeData><betaData></betaData></data></response>
----------
Empathy then reports that the login failed. I have verified that my accounts are still valid: they successfully connect using the website Meebo.
It is interesting that both Empathy and Pidgin are suddenly experiencing the same error. Thinking that the bug must be on AOL's side, I checked with other (non-Fedora) Empathy/Pidgin users, but haven't been able to find anyone else who could reproduce the bug.
The output of `rpm -ql --last` | head -75` is provided in the attachment.
This is filed against Empathy 2.28.2.
After performing a system update, Empathy is unable to login to AIM and ICQ. Interestingly, Pidgin is also experiencing the same error, reporting the problem as "Received unexpected response from https:/ /api.screenname .aol.com/ auth/clientLogi n". Empathy didn't specify what the problem was.
On the basis of that error, I ran Wireshark and watched the login attempt.
Empathy sends the following request to the server (with personal details omitted):
---------- api.oscar. aol.com/ aim/startOSCARS ession? a=[...] &f=xml& k=[...] &ts=1263348414& useTLS= 1&sig_sha256= [...]
GET http://
HTTP/1.0
Connection: close
Accept: */*
Host: api.oscar.aol.com
----------
The response from the server is then as follows:
----------
HTTP/1.1 200 OK
Date: Wed, 13 Jan 2010 02:06:54 GMT
Server: Apache
Content-Length: 286
Pragma: no-cache
Cache-Control: no-store, no-cache, must-revalidate
Keep-Alive: timeout=1, max=61
Connection: Keep-Alive
Content-Type: text/xml
<?xml version="1.0" encoding="UTF-8"?> developer. aim.com/ xsd/aim. xsd"><statusCode> 400</statusCode ><statusText> useTLS= 1 is not allowed for non secure requests. </statusText> <data>< ts>1263348414< /ts><upgradeDat a></upgradeData ><betaData> </betaData> </data> </response>
<response xmlns="http://
----------
Empathy then reports that the login failed. I have verified that my accounts are still valid: they successfully connect using the website Meebo.
It is interesting that both Empathy and Pidgin are suddenly experiencing the same error. Thinking that the bug must be on AOL's side, I checked with other (non-Fedora) Empathy/Pidgin users, but haven't been able to find anyone else who could reproduce the bug.
The output of `rpm -ql --last` | head -75` is provided in the attachment.