03-30-2016 04:55
03-30-2016 04:55
Hi, im trying to verify my suscriber endpoint with https schema.
My: url
https://backend.icarewave.com/CareWaveSynchronizations/api/fitbit/synchronize
When i change https to http everything works fine. When i use https result is "Subscriber has not been successfully verified".
Our certificate is Go Daddy Secure certificate authority - G2.
When i look into IIS logs no records about 2 request from fitbit found (as documentation say https://dev.fitbit.com/docs/subscriptions/#verify-a-subscriber 2 requests are send to endpoint).
I tried create request via runscope with https schema and subscriber endpoint is successfully verified.
What i'm doing wrong ?
Thanks in advance.
Answered! Go to the Best Answer.
03-30-2016 11:22
03-30-2016 11:22
Hi @CWMatej: You're probably not doing anything wrong. The issue is likely the Go Daddy Secure certificate authority - G2 because Go Daddy didn't follow proper procedure to get its root certificate included with the version of Java that Fitbit's servers use. You can either use a different certificate authority or try a crossover chain method with Go Daddy's G1 cert.
03-30-2016 11:22
03-30-2016 11:22
Hi @CWMatej: You're probably not doing anything wrong. The issue is likely the Go Daddy Secure certificate authority - G2 because Go Daddy didn't follow proper procedure to get its root certificate included with the version of Java that Fitbit's servers use. You can either use a different certificate authority or try a crossover chain method with Go Daddy's G1 cert.