Hello
I am having a problem authenticating with Twitter using OpenAuth
When I run the following command on our server:
curl --get ‘https://api.twitter.com/1/’ --header ‘Authorization: OAuth oauth_consumer_key=“N5cW9edCa3GyYBZy0y9g”, oauth_nonce=“563f57c556c880e021f4937158b0efcc”, oauth_signature=“s7hJ3OZxqFrk9uXbL%2B2gpULYslI%3D”, oauth_signature_method=“HMAC-SHA1”, oauth_timestamp=“1359363365”, oauth_token=“344037651-4wQpTB8n98E9AtjptYsMYzgQDjue0mAJ7NnLp8vA”, oauth_version=“1.0”’ --verbose
I cannot authenticate. Looking at the command output I get the following message:
subjectAltName does not match api.twitter.com
Our SSL certificate has the following Certificate Subject Name:
Not Critical
DNS Name: *.cvminder.com
DNS Name: cvminder.com
Can anyone explain when I am getting the above error and how I can solve my authentication issue?
Many thanks.
Ian Collier
Full output from the above command:
- About to connect() to api.twitter.com port 443 (#0)
- Trying 2a02:4e8:4:1050::5c3c:7b10… connected
- Connected to api.twitter.com (2a02:4e8:4:1050::5c3c:7b10) port 443 (#0)
- successfully set certificate verify locations:
- CAfile: none
CApath: /etc/ssl/certs
- 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 DHE-RSA-AES256-SHA
- Server certificate:
-
subject: serialNumber=bhNv2gOukwFRXUJbXzEsfrS96k/oIMJs; OU=GT60918638; OU=See www.rapidssl.com/resources/cps (c)13; OU=Domain Control Validated - RapidSSL(R); CN=*.cvminder.com
-
start date: 2013-01-16 00:56:17 GMT
-
expire date: 2014-01-18 12:25:02 GMT
-
subjectAltName does not match api.twitter.com
- Closing connection #0
- SSLv3, TLS alert, Client hello (1):
- SSL peer certificate or SSH remote key was not OK
curl: (51) SSL peer certificate or SSH remote key was not OK
