This feature requires you set up the deeplink URLs whitelist for your Dynamic app. See here.

The dynamic client authentication module enables social authentication.

​
Connecting to your users’ social accounts

Notice that all social options you use in code must be respectively enabled in your environment’s dashboard settings first!

You can prompt a user to connect their social accounts with the connect method in our social module. It returns a promise that resolves with no params on success, and rejects on failure.

Here’s how you can connect a user’s farcaster account, for example:

OutlinedButton(
    onPressed: () async =>
        await DynamicSDK.instance.auth.social.connect(
        provider: SocialProvider.farcaster,
        redirectPathname: '/login_screen',
    ),
    child: const Text(
        'Continue with Farcaster',
    ),
)

See here for a list of all our supported social providers — it will be the same list you see in your dashboard.

Not only can this method be used to sign a user in, but it is also able to link a social account to an already signed in user.

​
Adjusting app name in social connection dialogues

Social connection dialogues will derive the name of your app from the appName prop you used to initialize your client — read here.

So in order for your app’s name to be displayed correctly to your user when they are connecting their social accounts, you need to provide this prop.

You can read more about the social module here.

Was this page helpful?

Dynamic PackageWeb3Dart Package