I changed the URL of my discourse site, and promptly members started complaining that they could not log in. Exactly the problem reported in Changing domain names prevents Discourse ID from working. Looks like the fix is to empty the credentials via the rails console.
I thought the Regenerate credentials button would help but selecting that generated an error as well.
Seems to me this is worth investing in addressing, since it’s not unheard of to change the URL of your site. My feeling is that Discourse ID should auto correct itself in some way. Or at least there should be a way to refresh Discourse ID via the admin UI.
In our hosting, this is handled automatically. In self-hosted sites, it’s running into the issue you described. There is no event or screen in the admin UI where an admin indicates to the app that they are about to change the domain of the app, so we can’t act on it at the right time…
A similar issue happens with all the other social login providers, they need new apps to be created. Did you see any issues in the admin dashboard? I would expect problem checks to possibly have fired.
I don’t recall seeing any issues in the admin dashboard, but then I didn’t watch out for it either.
Can you add a button next to “Regenerate credentials” to delete the credentials? Or a JIT popup when disabling Discourse ID to ask if you want to delete the credentials? Either of those would have helped me to avoid having to go to the command line.
Will have a look at this shortly. My first instinct is not to add another button, it can be confusing when browsing these pages in normal times (i.e. outside of domain changes). But maybe disabling ID should clear the credentials upstream anyway. No harm in that, potentially, since re-enabling would create new credentials.
