为 discourse-openid-connect 正确地将客户端机密存储在数据库中

Question

I have used a Discourse Docker image to get Discourse running, and used the following openid-connect plugin so that users can signup / login to our forum via our web app which is using IdentityServer4

I can get it working if I don't require client secrets, but when I set it to require client secrets, authorization fails.

[plugin settings][1]

I added the client secret in the plugin as you can see the settings in the image, and then added the secrets in plain-text to the relevant cell in the database.

I assume the fact it works without requiring secrets but then fails when I require it, is because Discourse plugin will be processing the secret in some way, like sha256 etc, and that is why its failing, as I have stored the password in plain-text and its not matching the processed secret given by Discourse.

Does anyone have any ideas what process I would need to put my secrets through to store it correctly in the database, so that authentication succeeds? or is my issue likely something else?

Appreciate any help

Answer 1

Default type of secret is shared secret on IdentityServer. To define a shared secret you can use Sha256 extension method . Run sth like the code bellow for ur secret and save the result in DB

"secret".Sha256()

Read more about secrets here