Discussion for "REST API SSL certificate update"

lfcipriani · 2014-01-10T12:42:21.000Z

The exception says it’s unable to find a valid certification path. When doing a SSL request, the HTTP client needs to have access to a list of certificates that will be used to check if the server certificate is valid.

To fix this, you will need to find what path should be used for the HTTP client you are using AND if this path has all the certificates to be able to check for validity when trying to connect to api.twitter.com.

Usually you can find information about that path in the documentation of your language main libraries.

chcibelli · 2014-01-17T13:38:17.000Z

Hi, im using PHP and still doesnt work. Im getting “401” when call request_token

Where did you download the pem file?
What permissions did you apply to pem file?

Thanks,

chcibelli · 2014-01-17T14:08:04.000Z

Im getting 401 when trying to request_token, could be related to this update? It worked perfect and start failing on jan 14th

Thanks,

beercodebeer · 2014-01-17T16:49:44.000Z

Hi Christian.

I don’t know if this is related to your issue, but the timing looks right. Twitter is now enforcing that all api calls be made via https.

https://dev.twitter.com/discussions/24239

I missed this update, and only just today noticed that one of my applications has been failing to authenticate users and post tweets on their behalf for the past few days. I changed all the api endpoints in my twitter library to use the https protocol, and now it’s working properly again.

Hope this helps.

The405radio · 2014-01-17T23:02:00.000Z

got a fix from a developer…now seeing this: Exception: Server error: error setting certificate verify locations: CAfile: twitter.crt CApath: /etc/ssl/certs

Thoughts?

coldfusioner · 2014-01-17T23:25:11.000Z

Yep, I couldn’t edit my post after comments were added. Typo on my part…

coldfusioner · 2014-01-17T23:28:03.000Z

@beercodebeer same issue here, I missed that post too. A few of our older servers running CF9 that haven’t been updated stopped working like @chcibelli reported. Looks like I’ll have to make time to patch those bad boys. Thanks y’all.

lfcipriani · 2014-01-28T18:58:21.000Z

This code is usually related to wrong assignment of app tokens in your configuration. Please do the recheck and try again. Thanks

coldfumonkeh · 2014-01-29T13:54:32.000Z

http://www.verisign.com/repository/roots/root-certificates/PCA-3G3.pem

sastha · 2014-01-30T03:17:57.000Z

If we run below command"

keytool -import -v -alias PCA-3G3 -file C:\JRun4\jre\lib\security\PCA-3G3.pem -keystore C:\JRun4\jre\lib\security\cacerts -storepass changeit

It throws
keytool error: java.lang.Exception: Input not an X.509 certificate

Ryan_Veitch · 2014-02-27T10:34:18.000Z

Hi, I’m a third year Engineering student, my project requires me to read/write tweets using an Arduino Uno Rev 3 with ATmega328P, when i attempt to tweet, I get the following error:
{“errors”:[{“message”:“SSL is required”,“code”:92}]}
Update failed

I was hoping someone could offer some advice on how to get this to work?

Thanks,
Ryan.

manu60802231 · 2014-03-04T21:19:47.000Z

Hello,
I was using the twitter filter streaming api without any issues. From last two days i started getting error " SSL peer shut down incorrectly" there after if i try to reconnect I get 401 error. But if I try to reconnect after some minutes it will work again SSL error will repeat after some time.

I am using Apache HTTP client with following SSL config
SSLContext sslcontext = SSLContexts.custom()
.loadTrustMaterial(trustStore)
.build();
// Allow TLSv1 protocol only
SSLConnectionSocketFactory sslsf = new SSLConnectionSocketFactory(
sslcontext,
new String[] { “SSLv3”, “TLSv1” },null,
// new String[] { “SSL_RSA_WITH_RC4_128_MD5” },
SSLConnectionSocketFactory.STRICT_HOSTNAME_VERIFIER);
httpclient = HttpClients.custom()
.setSSLSocketFactory(sslsf)
.build();
Also i imported twitter certificate using below command

keytool -import -v -alias twitter-cert -file /opt/java/certs/twitterapi.cer -keystore /opt/java/jdk1.7.0_51/jre/lib/security/cacerts -storepass changeit

Still I am getting this issue.

Waiting for your help.

ckryanco · 2014-04-12T05:06:00.000Z

@beercodebeer – Do you know if something has just changed to make this not work? This approach worked perfectly until yesterday, when I started getting the dreaded connection failure again…

beercodebeer · 2014-04-17T00:38:53.000Z

Hi @ckryanco. I did have to repeat this process recently. It looks like Twitter recently updated their SSLs again (probably related to the Heartbleed bug), but following the steps above resolved the recurring Connection Failure error for me.