The Discourse team announces that Discourse ID is now available for all hosted and self-hosted sites, aiming to provide a seamless, single-click login experience without requiring separate accounts or complex social login configurations rishabh. Users can enable the feature via the admin panel, and Meta.discourse.org is migrating to Discourse ID by November 30, 2025, encouraging users to link their existing accounts.
The discussion highlights several user experiences and technical nuances. Positive feedback includes the ease of use and automatic avatar synchronization NateDhaliwal, eisammy, and hugh. However, some users encountered issues: craigconstantine reported a redirect bug on Safari which was attributed to an Apple App Site Association file pmusaraj, and Jagster struggled with account creation conflicts. A common hurdle was connecting Discourse ID for accounts with 2FA enabled; users were advised to temporarily remove 2FA methods to link the ID Moin, itsbhanusharma, and gingerbeardman noted that misleading banners caused confusion, prompting a fix from the team rishabh.
Administrative concerns were raised regarding default settings and privacy. Canapin and Jagster debated enabling the feature by default, citing EU regulations and GDPR concerns regarding data storage and user consent. The team clarified that while Discourse ID will be an easy option for new self-hosted instances and potentially default on hosted sites, it will not be automatically enabled on existing communities to avoid intrusive changes pmusaraj, pmusaraj. The team also confirmed that traditional SSO methods like Google and Discord can coexist with Discourse ID rishabh. Finally, localization efforts are underway, with French translations expected soon, relying on browser language detection stephtara, pmusaraj.
We’re happy to announce that Discourse ID can now be enabled on all Discourse sites, including both hosted and self-hosted sites!
Discourse ID provides a faster login experience across participating Discourse sites so you don’t have to create separate logins for each Discourse you visit and you can join any participating Discourse sites with just one click. It also lets Discourse admins offer a simplified login experience, with support for social logins with no setup or configuration needed.
Every time you see “Log in with Discourse ID” on Discourse sites in the wild, you’re seconds away from jumping into conversations! No more juggling accounts — just log in and go.
If you don’t see ID available on a site, note that it is a new feature and some communities have not opted in yet. Ask your community admin to enable it (or check again later).
We are replacing Meta’s current social login methods with Discourse ID — which includes social logins out-of-the-box — on November 30, 2025.
All you need to do is sign into Meta with a Discourse ID account using the same email address, or go to your account preferences and connect Discourse ID as an associated account.
There’s a UX thinko: I’m on Safari on a Mac, and when I try to login, here on Meta, using my shiny new Discourse ID: I successfully pass the authentication on Discourse ID, and then it redirects me . . . to the Discourse App. I do have that app installed, but it should continue, in Safari, to redirect me to Meta. (And of course Meta does point out, at the top of my Safari window, that I can open Meta in the App.)
Oh, sorry about that, we have an over-eager Apple App Site Association file on meta at the moment. I made an update, but sadly it will take up to 24 hours for the Apple CDN to work. I’ll check then to make sure it is fixed.
Just can’t get it work. Here, I mean. Connecting fails all the time. It doesn’t accept password and google/facebook tries to create totally new account. This is actually the very first time ever I couldn’t use login and/or create passkey.
Can we have tradition SSO (Google, Discord, etc) in addition to Discourse ID? We are considering implementing this, but dont want to force users to migrate their accounts
Yes! You can choose to have both types of options enabled or ask users to switch over to ID and phase out the old login methods (as the migration aspect is optional).
The only drawback I can think of is that you’ll have to make sure those login configurations are up to date and working correctly, and ensure that users are not too confused by the various login options presented as ID ships with them out of the box.
The issue here or might be is that users must know they have to create an account to id.discourse. That isn’t something new and that is the way how SSO works. But I don’t know how to explain to users why they should do that, when there is another SSO options.
Unless CDCK has plans to monopolize registrations and stop to support Google etc. So, I don’t totally understand meaning of that.
Do you intend to enable this authentication method by default in the future? The usefulness seems limited if it is not. I wouldn’t be surprised if only a few sites enable it, just because admins in general don’t know what it is or are not aware of it.
Yes, for self-hosters we are working on including Discourse ID as an easy option for the initial setup. We’d like to see if it can let people start a new instance without the dreaded email step, because with Discourse ID, users don’t need email for setting up their first account. They will need email eventually, but postponing that arduous process even a little bit is useful.
We are also looking to enabling Discourse ID by default on signups in our hosting.
I’ve been looking forward to Discourse ID being ready, and it works great! I especially like that it takes alternate email addresses into account, so I can use the same Discourse ID for sites that use different email address as their primary ones.
There are already so many Discourse sites in the wild that I’d be happy if the setting was enabled automatically via a site update as long as admins notified. Or perhaps better, a choice popup in the backend after the update that let us choose if we want to enable or disable this feature.
Discourse ID provides a faster login experience across participating Discourse sites so you don’t have to create separate logins for each Discourse you visit and you can join any participating Discourse sites with just one click. It also lets Discourse admins offer a simplified login experience, with support for social logins with no setup or configuration needed.
Enabling Discourse ID on your community
Using Discourse ID
Using Discourse ID for your meta.discourse.org account