Message de Dropbox

Bonjour Ged marcophile,

Merci de votre message sur la communauté Dropbox!

Je vous invite à regarder dans l'email quelle est l'adresse email d'envoi, si vous voyez "no-reply@dropbox.com", il s'agit bien d'une communication officielle.

Pouvez-vous aussi transférer le texte de l'email afin de voir ce qu'il en est?

Merci par avance de votre réponse!

Daniel

Le message vient bien de no-reply@dropbox.com

Voici le texte

Hi Union, We’ll be updating our access tokens and some of our ID formats in September—you’ll want to review to ensure your app handles these correctly. Action required: ID formats

Beginning on September 30th, 2021, the Dropbox API will begin returning new namespace IDs as strings with the format String(pattern="[-_0-9a-zA-Z:]+"). That means that namespace IDs may contain letters, numbers, and the symbols “-”, “_", and “:”.

Namespace IDs refer to folder permission spaces. They are used in the API to refer to shared folders, team folders, and root folders. They may also be used in path arguments. Field names such as ns_id, target_ns_id, previous_parent_ns_id, new_parent_ns_id, root, namespace_id, shared_folder_id, parent_shared_folder_id, team_folder_id, team_folder_ids, root_namespace_id, home_namespace_id, member_folder_id and nspath would be impacted by this change.

While the Dropbox API specification has indicated the string data type for these fields, the actual values returned by the API have been string representations of integers. We’re notifying you in case your application’s code and data storage can’t handle this string pattern. If your app already handles and stores these values as string types rather than integers, no action is required.

Action required: tokens and permissions

As a reminder, on September 30th, 2021, the Dropbox OAuth flow will no longer return new long-lived access tokens. It will instead return short-lived access tokens, and optionally return refresh tokens. Existing tokens are not impacted.

Apps that require background access will need to update their code to use refresh tokens, which is made easier by using our updated SDKs. All other apps should ensure that users are directed to re-authorize upon token expiration.

The Dropbox API now supports more granular permission scopes. While you review your application’s OAuth flow, be sure to check for scopes that may not be required.

For detailed instructions, please see:

• Dropbox OAuth Guide
• Blog post — Now Available: OAuth scopes and enhanced permissions
• Blog post — Migrating App Permissions and Access Tokens

Platform updates

As you review these changes, be sure to check out the latest additions to the Dropbox platform. The Dropbox developer blog is the best place to find developer feature announcements, tutorials, and resources.

For example, we’ve recently updated the API to enable creating and updating Dropbox Paper docs. These paper documents are accessible through the file APIs.

If you have any questions, visit our developer forum or submit a ticket.

Thanks!
- The Dropbox Platform Team

Merci de vos conseils

Cordialement