Notification Subscriptions using HTTPS results in SSLHandshakeException error

[ParkJinsu]

Hello.

Notification Subscriptions using https result in SSLHandshakeException

what problem???

[ParkJinsu]

hello

Notification Subscriptions using https result in SSLHandshakeException

We using  TLS(v 1.0)/SSL protocol for the subscriber endpoints.

we using GeoTrust Global CA-RapidSSL CA   *.everhealth.co.kr

https://www.geotrust.com/resources/repository/legal/

help me, please

[JeremiahFitbit · Accepted solution]

According to https://www.ssllabs.com/ssltest/analyze.html?d=wapinew.everhealth.co.kr , you are using SNI. Fitbit does not support TLS+SNI. You will need to use standard TLS.

[ParkJinsu]

I have a couple of question

1.I wonder why your service don't support TLS+SNI protocol.

2.We have an apache server on linux and the server has .conf file including 6 virtual host options. Do you think that would be the problem?

3.we have used 2.2.15 version of apache http server which support SNI. What if we downgrade our apache server to 2.2.11 which doesn't support SNI?

We are in big trouble with this problem. Any advice would be very helpful for us.
Thanks

[JeremiahFitbit · Accepted solution]

---

@ParkJinsu wrote:

1.I wonder why your service don't support TLS+SNI protocol.

---

This is a limitation of the version of Java and HTTP library that we are using. We will support TLS+SNI at some point in the future.

---

ParkJinsu wrote:

2.We have an apache server on linux and the server has .conf file including 6 virtual host options. Do you think that would be the problem?

3.we have used 2.2.15 version of apache http server which support SNI. What if we downgrade our apache server to 2.2.11 which doesn't support SNI?

---

The server that is responding to HTTPS traffic must only be responsible for a single hostname. You can learn more about TLS+SNI at http://en.wikipedia.org/wiki/Server_Name_Indication . Unfortunately, I can't provide support for issues beyond the scope of the Fitbit API.

[ParkJinsu]

I appreciate your quick reply.
Eventually, I solved the problem of SSLHandshakeException by setting some options in apache conf but I faced an another problem. Request of your fitbit server doesn't have a body information.
That is what we received from fitbit server

/////////////////////////////////////////////////////
[method] POST
[url] /wellness_sp_v2/external/fitbit/subscription
[headers] X-Fitbit-Signature=2yIwm+f8l7kqBDSYs+9ocSHh9SE= content-length=113 content-type=application/json host=wapinew.everhealth.co.kr connection=Keep-Alive
[body]
/////////////////////////////////////////////////////

Body information is empty so it makes NullpointException in our web service.
I think it's not a problem of fitbit server. It might be a problem of our server.
I don't know what is wrong with that. What should I do more?

Thanks in advance

[JeremiahFitbit · Accepted solution]

In your application settings at https://dev.fitbit.com/apps , make sure that the "Type" is set to JSON body.

That example says "content-length=113", so there should be 113 octets (characters in this case) of data in the body.

[ParkJinsu]

I solved !!

Thank you very mush!!

Have a nice day!!

[bkevern]

We've bumped into this same problem with the FitBit API.  The note below indicates that you will support TLS+SNI at some point in the future, but that note was written over a year ago and I still don't see this support.  Is it sill the case that you don't support TLS+SNI?  Is there any plan to upgrade?

[JeremiahFitbit]

@bkevern: Fitbit does not support TLS+SNI extension at this time, but does support the latest, TLSv1.2.