Not Receiving Files from Fitbit- ElevanceHealth

[Raju-SOA]

We have been not receiving files from fitbit from 4/7 .

File format : FTB_LPR_MBR_SRVC_*.txt

Can you please check and confirm if the connectivity from fitibit end to below API is intact.

We see there is a traffic drop from 4/4 10 PM ET , when we check in fitbit portal, finding few ssl handshake errors as well . PFB SS with details.

API- https://api.anthem.com/v1/wellnesspartners/fitbit/notification

Please note that we have renewed the certificate for api.anthem.com during the same time and as part of which signers certificates changed from Entrust to SSL.com .

So fitbit should be having ssl.com signers for making the connectivity , as traffic is still coming intermittently please check from your end and confirm .

Certificate details are shared below.

Issuer details	Serial Num	Thumbprint
Entrust OV TLS Issuing RSA CA 1 (Intermediate)	6fe63ede5fc1c03afb6d7a85bd3a156d	caaac3e16bd24266887cc85673c018f46a139b0f
SSL.com TLS RSA Root CA 2022 (Root)	6fbedaad73bd0840e28b4dbed4f75b91	ec2c834072af269510ff0ef203ee3170f6789dca

[GordonFitbit]

Hi @Raju-SOA 

About the time your subscriber stopped sending notifications is about the time we updated our SSL version to CA 2022.  Let me check with the engineering team on this problem.

[Raju-SOA]

Hi Team,

Do we have any more update to this issues , we still don't see files coming in . Its impacting business , please respond soon to avoid any further impact

[Raju-SOA]

Hi ,
Please share an update here as this is pending from long without any resolution 

[GordonFitbit]

Hi @Raju-SOA 

I believe we have implemented a fix for the webhook notifications.   Would you please test again and let me know the results?

[Raju-SOA]

hi @GordonFitbit ,
 we still see SSL handshake exception for the API , Can you please confirm if below signers certificates are supported by fitbit. We migrated to this SSL.com signers on 4/4 post which we are seeing this issue .

Also please let us know if there is any way we can meet over a scheduled meeting to discuss this further.

Issuer details	Serial Num	Thumbprint
Entrust OV TLS Issuing RSA CA 1 (Intermediate)	6fe63ede5fc1c03afb6d7a85bd3a156d	caaac3e16bd24266887cc85673c018f46a139b0f
SSL.com TLS RSA Root CA 2022 (Root)	6fbedaad73bd0840e28b4dbed4f75b91	ec2c834072af269510ff0ef203ee3170f6789dca

[Raju-SOA]

Hi @GordonFitbit any update on above scenario please

[GordonFitbit]

Hi @Raju-SOA 

We implemented another fix at the end of last week.  Would you please try again to see if the error has been resolved for you?

[Raju-SOA]

HI @GordonFitbit ,

Still We are facing the issue that we are unable to process the files from fitbit. Please help us to resolve it

[GordonFitbit]

Hi @Raju-SOA 

What error messages are you getting now?   Have you tried deleting your subscriber in the developer portal and re-creating it?