Dropbox

Members sign in with their Dropbox account, in the system browser.

Before you start

Console	Dropbox App Console
Endpoint group	Social Login
Email	Returned, and verified — Dropbox can match an existing account
Signs in	In the browser

Create the app

1. Open the Dropbox App Console and press Create app.

2. Choose Scoped access as the API.

3. Choose App folder as the access type. Sign-in touches no files, and this is the narrowest option that lets the app exist.

4. Name the app. Dropbox names are globally unique, so a generic community name may be taken.

5. Open the Permissions tab and tick account_info.read. Submit.

6. Open the Settings tab and add the redirect address under Redirect URIs: the string from Memberside → API Keys → Social Login → Dropbox, which looks like https://yoursite.com/wp-json/memberside/v1/social/callback/dropbox.

7. Copy the App key and App secret from the same tab.

Set permissions before your first sign-in. A token issued before a scope was added does not gain it retroactively.

Development mode

A Dropbox app starts in development, where it may authorise a limited number of accounts. Press Enable additional users on the Settings tab, or apply for production status, before opening sign-in to a community.

What to paste into Memberside

Under Memberside → API Keys → Social Login → Dropbox:

Field	Value
Client ID	The App key
Client secret	The App secret

When it does not work

Symptom	Cause	Fix
“missing_scope”	account_info.read was added after the first sign-in	Tick it, submit, and sign in again
Sign-in fails after a number of members	The app is still in development	Enable additional users, or go to production
The redirect is refused	The URI is not in the Settings tab list	Add it exactly
The app name is rejected	Dropbox app names are globally unique	Pick another