Use it for internal tools in organizations that still run on it.
Copy the redirect URI
In the Authdog console, select the project and environment, open Authentication > Providers, find Yammer, and click Enable. Copy the redirect URI shown in the form:
https://identity.authdog.com/api/v1/callback/<connectionId>Create the application
- Register a client at Yammer's developer page.
- Set the Redirect URI to the redirect URI from Authdog.
- Copy the Client ID and Client Secret.
Configure Authdog
| Field | Value |
|---|---|
| Client ID | The client identifier from the provider |
| Client Secret | The client secret from the provider |
Save, then toggle the connection active.
What Yammer returns
Authdog requests the provider's default scopes and reads the profile from https://www.yammer.com/api/v1/users/current.json.
The current-user endpoint returns the Yammer user id, full name, email, and network.
Yammer identities are network-scoped, and Microsoft has been migrating them into Viva Engage. For new deployments, prefer Microsoft or an Enterprise SSO connection to Entra ID.
Test it
- Open your environment's hosted sign-in page, or link to
https://identity.authdog.com/api/v1/signin/<connectionId>. - Select the Yammer button and complete the flow.
- Confirm the user appears under Users in the console with a Yammer identity linked.
Troubleshooting
| Symptom | Cause |
|---|---|
invalid_client |
The client was registered in a different Yammer network |
| Redirect or callback URL error | The URI registered with the provider does not match Authdog's exactly |
| Works in one environment only | Each environment has its own connectionId, and so its own redirect URI to register |
Related
| Read | To learn how to |
|---|---|
| Connectors | Set up any other social provider |
| Microsoft | Use the current Microsoft identity instead |