Thanks! Let me recheck after sometime.
This is not a bug, but the current setup of how the OAuth system works.
There is an existing feature request you might want to add your vote to and where you can follow any progress.
I was most likely wrong 
I see a difference between the feature request to make the forum stand out more and the issue where “Discourse” is displayed instead of the forum title.
The example in the feature request shows the forum’s name “CAN Discourse”
This topic reports that instead of “into FAKTout” Discourse ID only shows “Discourse”
Showing the correct name seems to work for other forums but not for this one. So I am not sure this is “how the current setup works”
Ah maybe I read it too hasty, thanks. I see the same thing on other forums though, hence I thought it was the regular way. Let me investigate more
(post deleted by author)
Yes, sounds good, will do
Same, it could be that the meta data has been pushed before the title was changed. Can you update the title to something else, save, and change it back to what you want? It could be that resaving the setting will trigger a resync.
It didn’t help. I changed Admin → All Site Settings → title.
Does it pick the site name from this field?
I think it does but this is not my area. Other colleagues are looking into it too 
Ah ok try this, it worked for mine:
cd /var/discourse
./launcher enter app
rails c
SiteSetting.discourse_id_client_id = ""
SiteSetting.discourse_id_client_secret = ""
exit
This feels more like a workaround than a fix. How does this work for all the forums on the free plan and all other hosted sites using Discourse ID?
Thanks a lot. It worked.
Mine is a selfhosted plan.
Since you said it worked, I expected that. But it doesn’t answer my question about the process for forums hosted by Discourse. Needing their support whenever you update the name or logo doesn’t feel like a solution.
On our hosted sites, this re-registration is handled automatically I believe, if I read this correctly: (big if)
