I've developed some problems with the social zimlet recently. Looks like I can no longer add new twitter accounts. Existing accounts are still working fine.


  1. I click on "Add/Remove Accounts"
  2. and then on Add Twitter Account
  3. Then click the Go to Twitter button


Nothing happens at all. I've checked that time sync is good, it is. I've made sure that all the relevant proxy domains are allowed for that COS.

The only thing I see as an error is a XHR request in firebug:

Params:
HTML Code:
target	https://twitter.com/oauth/request_token
Request Headers:
HTML Code:
Host	     	 mail.<snipped>.com.au
User-Agent	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0
Accept	text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language	en-au,en-us;q=0.8,en;q=0.5,en-gb;q=0.3
Accept-Encoding	gzip, deflate
Accept-Charset	ISO-8859-1,utf-8;q=0.7,*;q=0.7
DNT	1
Content-Type	application/x-www-form-urlencoded; charset=UTF-8
Authorization	OAuth oauth_callback="oob",oauth_signature="%2FDU<snipped>xmZQax3Y%3D",oauth_version="1.0",oauth_nonce="<snipped>",oauth_signature_method="HMAC-SHA1",oauth_consumer_key="Xz2BK<snipped>2ww",oauth_timestamp="1312800305"
Referer	https://mail.<snipped>.com.au/zimbra/
Content-Length	0
Cookie	original_referer=padhuUp<snipped>VfgjWeFUo1aPvlNGB5F1j; lang=en; ZM_AUTH_TOKEN=0_3e034cc9<snipped>696d6272613b
Connection	keep-alive
Pragma	no-cache
Cache-Control	no-cache
Returned Results (in firebug - onscreen nothing happens):
HTML Code:
ERROR 500

Problem accessing /service/proxy. Reason:

    java.security.cert.CertificateException: d2:CN11:twitter.com1:O14:Twitter\, Inc.2:OU18:Twitter Operations6:accept4:true5:alias44:twitter.com:1727<snipped>9BB046BC198024:fromi130<snipped>e4:host11:twitter.com3:icn43:VeriSign Class 3 Extended Validation SSL CA2:io9:"VeriSign3:iou50:Terms of use at https://www.verisign.com/rpa (c)063:md532:34A7<snipped>066CFE18:mismatch5:false1:s32:1727D<snipped>B046BC198024:sha140:EA9DEFD633<snipped>C689F54A659D7F10E662:toi1343<snipped>000ee

Powered by Jetty://
snipped a couple of hashes in case they leak important info (not sure either way).

Is this something that twitter has changed? Or is it something likely to be wrong at our end? (ie: certificates?)

Cheers.