Yahoo

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

Before you start

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

Create the app

1. Open developer.yahoo.com/apps and create an app.

2. Set the Application Name to what members should see.

3. Choose Web Application as the application type.

4. Set the Redirect URI to the address from Memberside → API Keys → Social Login → Yahoo, which looks like https://yoursite.com/wp-json/memberside/v1/social/callback/yahoo.

   Yahoo rejects http and rejects a bare IP address. The site must be on HTTPS.

5. Under API Permissions, tick Profiles (Social Directory) with Read permission.

6. Create the app, then copy the Client ID and Client Secret.

The email arrives through OpenID Connect

Memberside asks Yahoo for the openid profile email scopes. An application configured only for the older profile API returns no address, and the sign-in then has nothing to create an account from. The permission above is what makes the profile available; the scopes are requested for you.

What to paste into Memberside

Under Memberside → API Keys → Social Login → Yahoo:

Field	Value
Client ID	The Client ID, sometimes shown as Consumer Key
Client secret	The Client Secret, sometimes shown as Consumer Secret

When it does not work

Symptom	Cause	Fix
The redirect URI is rejected at creation	It is not HTTPS, or it is an IP address	Use an HTTPS domain
Sign-in returns no email	The app has no profile read permission	Tick Profiles with Read
“INVALID_REQUEST”	The redirect differs from the registered one	Copy it again
The app disappeared	Yahoo removes apps with no successful calls over long periods	Recreate it