• IA_Jason
  • NEWBIE
  • 0 Points
  • Member since 2013

  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 2
    Questions
  • 5
    Replies
All SFDC customers who secure their domains using a GoDaddy's new G2 CA SHA-2 certificates will get this Java exception when making any outbound HTTPS connections (e.g. Outbound Messages). " javax.net.ssl.SSLPeerUnverifiedException " 

SFDC lists the G2 CA root certificate here as supported but the Java Exception above indicates that this is not the case.

https://developer.salesforce.com/page/Outbound_Messaging_SSL_CA_Certificates

It was recently announced that this new certificate was submitted and included in the latest Java update.

https://garage.godaddy.com/webpro/security/google-chrome-phasing-ssl-certs-using-sha-1/#comment-1813967035

When will SFDC update to the latest version of Java to include this new list of trusted certificates?
Salesforce seems to have a problem with our wildcard GoDaddy SSL certificate. The Outbound Messaging Delivery Status page show a message with a Delivery Failure Reason of "javax.net.ssl.SSLPeerUnverifiedException: The domain name <api.example.com> wasn't in the supported set of domain names in". Unfortunately SFDC truncates the end of the error. Switching to HTTP works as expected.

After some investigation we believe seems SFDC does not like our wilcard cert. The common name of our cert is *.example.com and this seems to cause problems. How can we work around this issue?
All SFDC customers who secure their domains using a GoDaddy's new G2 CA SHA-2 certificates will get this Java exception when making any outbound HTTPS connections (e.g. Outbound Messages). " javax.net.ssl.SSLPeerUnverifiedException " 

SFDC lists the G2 CA root certificate here as supported but the Java Exception above indicates that this is not the case.

https://developer.salesforce.com/page/Outbound_Messaging_SSL_CA_Certificates

It was recently announced that this new certificate was submitted and included in the latest Java update.

https://garage.godaddy.com/webpro/security/google-chrome-phasing-ssl-certs-using-sha-1/#comment-1813967035

When will SFDC update to the latest version of Java to include this new list of trusted certificates?
Salesforce seems to have a problem with our wildcard GoDaddy SSL certificate. The Outbound Messaging Delivery Status page show a message with a Delivery Failure Reason of "javax.net.ssl.SSLPeerUnverifiedException: The domain name <api.example.com> wasn't in the supported set of domain names in". Unfortunately SFDC truncates the end of the error. Switching to HTTP works as expected.

After some investigation we believe seems SFDC does not like our wilcard cert. The common name of our cert is *.example.com and this seems to cause problems. How can we work around this issue?

Hi all,

 

I am having issues with Streaming API. Actually I tried to use CometD.NET project but to no avail.

 

While trying to call 'handshake' I am receiving error 500.

 

First I call 'login' method from Soap API and get server URL from the login response.

The request headers:

 

POST /services/Soap/c/28.0/00Dg0000000XXXX/0DFg000000000XX/cometd/28.0/handshake HTTP/1.1

Content-Type: application/json;charset=UTF-8
Host: cs17.salesforce.com
Content-Length: 100
Expect: 100-continue

 

And the response:
HTTP/1.1 500 Server Error
Date: Mon, 02 Sep 2013 20:19:21 GMT
Content-Type: text/xml;charset=UTF-8
Connection: close

<?xml version="1.0" encoding="UTF-8"?>

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" >

<soapenv:Body>
<soapenv:Fault><faultcode>soapenv:Client</faultcode>
<faultstring>content-type of the request should be text/xml</faultstring>

</soapenv:Fault>

</soapenv:Body>

</soapenv:Envelope>

 

I suspect that the Server URL for Streaming API should be different. 

 

Is the URL for Streaming API different?

Or do you have any other ideas?

 

Kr,

Slawek

  • September 02, 2013
  • Like
  • 0