nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Child Item

Dropbox API server root certificate changes for .Net

rnash

Im currently using versions pre-7.0.0 in my .net apps, and none of my apps call DropboxCertHelper.InitializeCertPinning(), so I dont need to update right? Why isn't this required for .net like it is for java? Is there any way to test if my apps will still function after the new root cert takes effect, regardless of updating the sdk?

Thanks!

Find more posts tagged with

Comments

Spencer H

Hi there,

The three SDKs affected by the upcoming change (Java, .NET, and Python) were implemented differently. Older versions of Java and Python automatically pin the old certificates based on how those SDKs are built, while the .NET SDK only enables this behavior if you explicitly call `DropboxCertHelper.InitializeCertPinning()`.

Since testing this would depend on the server configuration, it's not possible to test the upcoming change ahead of time.

If you are using a version of .NET earlier than v7.0.0 and you are not calling the `DropboxCertHelper.InitializeCertPinning()`, then you aren't manually initializing the older certificate pinning logic and don't need to make an immediate update.