Renren signs users in with their Renren account, a Chinese social network with a long-standing user base in university communities.

## Copy the redirect URI

In the [Authdog console](https://console.authdog.com), select the project and environment, open **Authentication > Providers**, find **人人网 (Renren)**, and click **Enable**. Copy the redirect URI shown in the form:

```url
https://identity.authdog.com/api/v1/callback/<connectionId>
```

## Create the application

1. Register an application on the Renren open platform.
2. Set the callback to the redirect URI from Authdog.
3. Copy the **API Key** and **Secret Key**.

## Configure Authdog

| Field | Value |
| --- | --- |
| **Client ID** | The Renren **API Key** |
| **Client Secret** | The Renren **Secret Key** |

Save, then toggle the connection **active**.

## What Renren returns

Authdog requests the provider's default scopes and reads the profile from `https://api.renren.com/v2/user/get`.

The user endpoint returns the Renren user id, name, and avatar.

This connector does not return an email address, so users who arrive through it have a display name and an identifier only. Pair it with a method that collects one, or ask for an email after the first sign-in.

## Test it

1. Open your environment's hosted sign-in page, or link to `https://identity.authdog.com/api/v1/signin/<connectionId>`.
2. Select the Renren button and complete the flow.
3. Confirm the user appears under **Users** in the console with a Renren identity linked.

## Troubleshooting

| Symptom | Cause |
| --- | --- |
| `redirect_uri_mismatch` | The registered callback differs from Authdog's |
| 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](/docs/connectors) | Set up any other social provider |