Signup via mainstream socials

[erlend-sh]

Rauthy supports signup via external authentication providers.

Seeing as Weird/Rauthy is its own Identity Provider it may seem nonsensical to support signup via the closed-source incumbents. However, social sign-ins are not oppositional to Rauthy’s value proposition if you think of them strictly as an onboarding tool rather than a default method of sign in.

For Weird we would like to use Rauthy to eventually become our own standalone OIDC provider to compete with the IdP incumbents (Google, GitHub et.al.) in our own small way. But for first-time user registrations, it’d be a mistake to not support the “usual suspects” as a signup method, as that’s what the vast majority of people are used to, including on Weird’s competitors like linktree and biolink.

The proprietary login options could be challenged post-signup; in Weird’s case we’d wait maybe 2-3 months for the user to fully commit to our service, and then pop the question:

“Do you want to upgrade your login with more security and privacy features? Switch to our Weird-ID for passkey login, MFA and zero tracking!”

---

Essential auth providers

• GitHub
• Google
• Azure (Microsoft)
• Facebook
• LinkedIn

Other

• Discord
• GitLab
• Slack
• Apple
• Twitter/X
• Spotify
• Tidal
• Mastodon
• Lemmy
• Bluesky

If you’re wondering why we are adding a rather big bunch of providers: it’s not that we would enable the majority of these by default on weird.one

Rather, having them loaded up and ready within the Weird package makes it possible for more specialized community distros of Weird (other Weird-based communities) to make use of the specialized login paths, e.g. a music-taste community would likely want to enable login via Spotify/Tidal.

[zicklag]

MVP social sign-in complete! The next step is: #52.

@erlend-sh do we want to close this issue now, and open more specific ones, or leave this open as a tracking issue?