Hi,
I'm attempting to set up a webhook subscriber and so far I'm only getting failures with the cryptic error reason "SSLHandshakeException". It seems this is a Java exception (I guess that's what the Fitbit server uses) but it can be caused by a number of reasons.
My server at exist.io definitely supports TLSv1 as outlined in the API docs, but perhaps you don't recognise my SSL cert? It's not self-signed but it is verified by StartCom (perhaps a vendor Fitbit's library doesn't recognise?)
Any help would be appreciated.
Answered! Go to the Best Answer.
Best Answer
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
Fitbit currently uses Java 7 and StartCom is not a recognized certificate authority in that version. We will be supporting more certificate authorities in the future. For now, you will need to use another CA.
Best AnswerThanks Jeremiah, I figured as much. That's a bummer but I'll switch CAs I guess.
Best Answer
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
I've been testing various options such as turning on SSLv3 and resetting nginx to the default list of supported ciphers, but still no luck. Perhaps a cert issue?
Best Answer
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
Please send PM to me your application id.
Best Answer
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
Fitbit currently uses Java 7 and StartCom is not a recognized certificate authority in that version. We will be supporting more certificate authorities in the future. For now, you will need to use another CA.
Best AnswerThanks Jeremiah, I figured as much. That's a bummer but I'll switch CAs I guess.
Best Answer
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
Best Answer