I must be blind or something… 
Cannot find discourse_id_client_id and discourse_id_client_secret in the configuration of my sites. Only Enable Discourse ID. 
Any idea?
Is force https enabled?
Yes it’s enabled. I checked that.
You just need to enable it and the secret and id are auto generated.
There’s a rake task that you run to make it connect to the central server and create keys. That’s your the key and secret get created.
I don’t see it documented anywhere.
It should be easy enough to find in the source, but not so easy that I can find it on my phone after 5pm
1 Like
Really? 
OMG… 
Me neigher. I wonder if anyone who’s running a self-hosted Discourse has set this up, yet. 
rake discourse_id:register
No. I just tried it on a site that is up to date and simply enabling the setting generates the keys.
I think that the rake task was required for a while before it was publicly announced and now enabling the setting requests the keys automatically, which makes much more sense than having to run a rake task.
1 Like
Thank you, but this did not work:
Plugin name is 'discourse-docs', but plugin directory is named 'discourse-knowledge-explorer'
rake aborted!
Don't know how to build task 'discourse_id:register' (See the list of available tasks with `rake --tasks`)
Did you mean? discourse_ai:install:migrations
/usr/local/bin/bundle:25:in `load'
/usr/local/bin/bundle:25:in `<main>'
(See full trace by running task with --trace)
Is your forum up to date? Did you try simply enabling the setting from the UX? I just tried it on a site that is on the last beta release.
1 Like
About a week, maybe two, since the last rebuild.
Did you enable it? When you do it will generate the others. You don’t need to dim them out yourself.
1 Like
I did enable enable_discourse_id and got an error (in German):
enable_discourse_id: Du musst die Discourse-ID-Anmeldedaten („discourse_id_client_id“ und „discourse_id_client_secret“) konfigurieren, bevor du diese Einstellung aktivierst.
It says that I need to configure discourse_id_client_id and discourse_id_client_secret before ticking enable_discourse_id.
So it is a kind of hen/egg problem at the moment.
2 Likes
Odd. You might try upgrading and then filling a bug report.
Are you behind cloudflare or other reverse proxy that might deny the discourse server from connecting to your server? I’m pretty sure that I’d your behind cloudflare your won’t be able to make it work.
1 Like
Just upgraded to the latest version. I do not see the two options…
Nothing. My instances run on a Linux server “behind” an Apache webserver. I think pretty much straight forward as it is described in the howto run self-hosted instances.
Yesterday I set up another instance for testing a migration from another forum. I do not see the options there, too.
You turned the option off (if it was on) and then tried enabling it?
You will never set those values yourself.
1 Like
No, I am not able to turn it on. The error text says that I first need to setup client_id and client_secret.
That is what I meant with hen/egg problem. What problem was first or I cannot turn on without the values I cannot set because the boxes are not visible.
I think pfaffman tried to explain that while the error says that those settings need to be configured before enabling the setting, it’s not you but the software that should fill them.
Maybe Discourse ID fails to activate on my instance can provide some ideas for what else you could try.
1 Like
Sounds like it was an issue with the reverse proxy setup like I expected
Try turning on force_https. That’s a common problem with a reverse proxy since discourse can’t tell that it’s https
force_https is turned on since the beginning.
When I first logged into the new instance I installed yesterday it asked me right away if I want to turn on force_https.
But yes, Apache runs HTTPS and the reverse proxy is using port 8080 http on the Discourse Docker container. But somehow Discourse knows that it is running https anyway.
That’s my best guess. How did you turn on force https
In the admin area with the web browser. Should this be done on the console? Like
rails r "SiteSetting.force_https=true"
Just tried. Seemed to work, as it did not give any feedback on the console.
But I still do not see two new settings (in the web browser) for the client_id and client_secret.
1 Like