How Discourse ID works

[Moin]

Maybe the information about what to do after changing the domain name could be added to the first post:

@pmusaraj

If you have access to the Rails console, you can empty the client id and secret for the discourse id settings and then toggle off/on the Enable Discourse ID setting, it will trigger a new registration.

@在云端_裸奔

./launcher enter app
rails c
SiteSetting.discourse_id_client_id = ""
SiteSetting.discourse_id_client_secret = ""

[mcwumbly (Dave McClure)]

I added the following to the first post:

@rishabh

Reconfiguring ID after changing domain names

After changing your site’s domain name, to trigger a new registration you need to

1. empty the client id and secret for the discourse id settings
2. toggle off/on the Enable Discourse ID setting.

If you have access to the Rails console:

./launcher enter app
rails c
SiteSetting.discourse_id_client_id = ""
SiteSetting.discourse_id_client_secret = ""

[Moin]

I think I would have put the rails script right below step 1

@rishabh

1. empty the client id and secret for the discourse id settings

Those are hidden site settings, so there is no other way to change them than using the Rails console

config/site_settings.yml

[0cjs (Curt J. Sampson)]

Can someone tell us about the higher-level of goals of creating this Discourse ID identity provider? I don’t see anything bad about this, but I’d like to see if there are any good points I’m missing.

It seems to me that for those who use GitHub, Google, Apple or Facebook, there’s no advantage to creating a Discourse ID since either way you’re doing a “one-click” (well, a very few clicks) registration or login to a Discourse site either way. So why is the option provided? Just for consistency?

For keeping an account separate from GitHub/Google/etc., Discourse ID seems to make sense. I assume it provides 2FA of some sort if you’re using an e-mail address and password to authenticate?

And last, can Discourse ID be used with other, non-Discourse systems? It looks as if technically it can be an ID provider for pretty much anything that wants to use it, but is this encouraged? Frowned upon? Something that Discourse ID is likely to break at some point?

I’m interested in general in who’s providing identity and why, for both digital sovereignty reasons and just “get away from Google/MS/etc.” reasons, so understanding what’s going on with alternate identity providers is of great interest to me.

[pmusaraj (Penar Musaraj)]

There are a few higher-level goals, but generally speaking, it boils down to two main advantages. For admins, they don’t need to configure and maintain Github, Google, Apple, Facebook logins. Each of these on its own is not too hard to set up and maintain, but it’s multiple steps as well as maintenance. And in Apple’s case, cost.

For the end user, there is not a huge difference at this time. In the long run, if enough communities adopt Discourse ID, we hope to offer a better centralized interface on ID (for the communities a user joins) controls for notifications, customization of user accounts, etc. And better discovery for new communities.