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.
I see this message when I try to activate Discourse_id on my test system (3.6.0.beta2-latest):
enable_discourse_id: You must configure Discourse ID credentials ('discourse_id_client_id' and 'discourse_id_client_secret') before enabling this setting.
I use a local Oauth server for OIDC here (keycloak). Maybe the two methods are interfering with each other??
I don’t think it interferes with OIDC, but if your instance is not available on the Internet, ID registration will not work. The Discourse ID identity provider has a verification mechanism in place for the Discourse instances that initiate the registration process.
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