Social login still feels like a fairly new thing in Dexie Cloud. Until quite recently (dec 2025), the built-in option was email one-time passwords (OTP). That worked well, but many applications also want users to sign in with an account they already have.
Since then, Dexie Cloud has added built-in social login, and the list is growing. Facebook, LinkedIn, and Discord are now available alongside Google, Microsoft, Apple, and GitHub.
There is a little setup involved. For each provider you want to support, you create an application in that provider’s developer console, configure a callback URL, and copy a client ID and secret into Dexie Cloud Manager.
That part is not especially exciting. Every provider has its own terminology and its own place for the relevant settings.
Dexie Cloud Manager helps by linking directly to the configuration section for each provider. Once you are in the right place, filling in the fields is usually quite manageable — and if you get stuck, ChatGPT or Gemini can help explain what a particular provider is asking for. And the user consent will present your company and logo instead of some intermediate brand that many other zero-config solutions may offer.
Once a provider is configured, the rest is deliberately boring. Dexie Cloud handles the OAuth redirect, exchanges the authorization code, retrieves the user’s identity, and returns the result to the application.
The application does not need a separate authentication implementation for Facebook, LinkedIn, Discord, or the other providers. It gets the same Dexie Cloud authentication flow whichever button the user chooses.
Social login can also be enabled alongside email OTP. That makes it possible to offer a familiar sign-in button without taking away the simple email-based fallback.
The built-in providers currently include:
Under the hood, the integrations use each provider’s standard endpoints. LinkedIn uses OpenID Connect, Facebook uses its Graph API, and Discord uses its OAuth2 user endpoint.
Some applications need an identity provider that is not on the built-in list. Dexie Cloud also supports custom OAuth 2.0 and OpenID Connect providers.
A custom provider can define its authorization, token, and user-info endpoints, optional JWKS URI, identity field, scopes, display name, and icon. PKCE is enabled by default and can be configured per provider.
User identity mapping is configurable too. An application can identify users by email, by an opaque email-derived identifier, or by a provider-specific identity such as discord:123456789.
The nice thing about social login in Dexie Cloud is not that it makes provider setup disappear. It does not. You still have to create and configure an application with each provider you want to support.
The nice thing is that this is the part you do once. Dexie Cloud Manager points you to the right settings, and Dexie Cloud takes care of the authentication flow afterwards. With a little help from the documentation — or from an AI assistant when a provider’s console is confusing — getting from “I want Facebook, LinkedIn, or Discord login” to a working local-first application is surprisingly straightforward.
Learn more in the Dexie Cloud authentication documentation.
Social login without the usual detour was originally published in Dexie.js on Medium, where people are continuing the conversation by highlighting and responding to this story.
© 2014-2025 Awarica AB
Browser testing via
Made with love for great people.
Read Terms & Conditions and Privacy Policy.