Subscription Endpoint Verification problem on dev.fitbit.com

[piotr-zywien]

Hi @JeremiahFitbit or anyone else who can help,

I know this has been discussed, however I am not using a GoDaddy cert, but a DigiCert cert and am running a pretty tight schedule, to migrate my app to OAutho2 by the 1st... Unfortunetely, I can't even add or change a subscription endpoint to verify correctly with Fitbit...

I use https://server.domain.com/fitbit/auth/callback?verify=<keyProvidedByDevFitbitPage>

and this fails to verify, even though when I execute:

https://server.domain.com/fitbit/auth/callback?verify=<keyProvidedByDevFitbitPage>

and

https://server.domain.com/fitbit/auth/callback?verify=<keyNotProvidedByDevFitbitPage> 

they yield 204 and 404 respectively, just like they should... Can anyone please help? 😞

Thanks sincerely,

Piotr.

[FedericoArg]

Once you added your endpoint in your application settings you need to copy the Verification Code, paste it somewhere in your app and use that to verify your subscriber. Be sure you are copying the entire text and not the "..." part

[JeremiahFitbit]

Have you verified that your TLS certificate is properly installed? Can you cURL it without a security error?

curl -X POST https://your-app.com/fitbit/subscriber