Your workflow is unique 👨‍💻 -  tell us how you use Dropbox here.

Forum Discussion

phunction's avatar
phunction
Helpful | Level 5
2 months ago
Solved

Root certificate changes

Hi, I received an email stating that:

...you own one or more active Dropbox API apps using a version of an official Dropbox SDK with an outdated certificate trust store...

However when reading the blog post, it states for the .net sdk

  • .NET SDK v7.0.0 or greater
    • Note that apps using older versions of the .NET SDK are only affected if they call DropboxCertHelper.InitializeCertPinning().

I don't use DropboxCertHelper.InitializeCertPinning(), so I want to clarify that my app will be OK, and I don't have to rush out a change before January?

Thanks

API
  • Eathen cole 3's avatar
    Eathen cole 3
    2 months ago

    Hi there 

    You’re absolutely right to double-check this — Dropbox recently updated their SDKs due to changes in certificate trust stores, but the impact depends on how your app handles certificate pinning.

    If your .NET app does not call Dropbox Cert Helper. Initialize Cert Pinning(), then you’re not affected by this change. The issue only impacts apps that manually initialize the older certificate pinning logic.

    So as long as:

    You’re using a Dropbox .NET SDK (even below v7.0.0), and

    You don’t call Dropbox Cert Helper. Initialize Cert Pinning() anywhere in your code,

    then you’re completely safe — there’s no urgent need to update before January. 

    Still, it’s good practice to plan an SDK update when possible to stay aligned with Dropbox’s latest security improvements and bug fixes.

    Hope that clears things up! 

3 Replies

Replies have been turned off for this discussion
  • Eathen cole 3's avatar
    Eathen cole 3
    Helpful | Level 5
    2 months ago

    Hi there 

    You’re absolutely right to double-check this — Dropbox recently updated their SDKs due to changes in certificate trust stores, but the impact depends on how your app handles certificate pinning.

    If your .NET app does not call Dropbox Cert Helper. Initialize Cert Pinning(), then you’re not affected by this change. The issue only impacts apps that manually initialize the older certificate pinning logic.

    So as long as:

    You’re using a Dropbox .NET SDK (even below v7.0.0), and

    You don’t call Dropbox Cert Helper. Initialize Cert Pinning() anywhere in your code,

    then you’re completely safe — there’s no urgent need to update before January. 

    Still, it’s good practice to plan an SDK update when possible to stay aligned with Dropbox’s latest security improvements and bug fixes.

    Hope that clears things up! 

  • Spencer H's avatar
    Spencer H
    Icon for Dropbox Staff rankDropbox Staff
    2 months ago

    Hi there,

    Thanks for sharing that clarification! Just confirming that this is correct -- older versions of the .NET SDK are only affected if they call `DropboxCertHelper.InitializeCertPinning()`. If your app doesn’t use this method, no immediate update is needed before January 2026.

    Appreciate your response here!

About Discuss Dropbox Developer & API

Node avatar for Discuss Dropbox Developer & API
Make connections with other developers

The Dropbox Community team is active from Monday to Friday. We try to respond to you as soon as we can, usually within 2 hours.

If you need more help you can view your support options (expected response time for an email or ticket is 24 hours), or contact us on X, Facebook or Instagram.

For more info on available support options for your Dropbox plan, see this article.

If you found the answer to your question in this Community thread, please 'like' the post to say thanks and to let us know it was useful!