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.
I moved this to a separate topic… do you see any errors in /logs on your instance? It should output some more details there on what is not working under the hood during the registration process.
I would like to understand it a bit more from the technical side.
On my instances, I use OIDC authentication with an external identity provider (Keycloak 26). Discourse ID looks very similar; it is just a different IDP server hosted by Discourse.org. And the error messages (client ID and secret missing) are also reminiscent of the classic OAuth flow. Does this mean that Discourse ID will be activated as an additional IDP authentication path? Because only then would it be useful for my use case. ???