The discussion addresses an issue with LinkedIn OIDC authentication in Discourse, where users encounter a “Value doesn’t match the required format” error when entering a valid client secret. haydenjames identifies the problem as a validation bug in Discourse’s regex check, which incorrectly rejects valid secrets. haydenjames resolves it by bypassing the UI validator and directly updating the secret in the database. The issue is linked to a known bug that needs patching, with a reference to a related pull request. PCPal thanks the contributor, noting that the fix resolves their SSOID issues and acknowledges potential problems with Microsoft as well.
I was only able to find this locked thread:
I tried to regenerate the secret key:
But still get this error:
linkedin_oidc_client_secret: Value doesn’t match the required format.
I’m 1000% sure the key is cut and pasted correctly. I’ve already setup X, Google, Github and others without issue.
Is there a known issue still?
So, I was able to solve this. Its a validation bug on the Discourse side the regex in the Discourse setting hasn’t caught up yet, so the admin UI rejects perfectly valid secrets with “Value doesn’t match…” error.
Go it to work by bypassing the validator and writing the secret straight to the DB. Now it works:
So probably this needs to be patched again as that’s the more acceptable and safer solution.
Ah! Thanks for sharing. I recently moved my forum to this very professional setup, as shown… And thought that the digital moving had caused my SSOIDs to break… Also Microsoft is defective in my case… Will investigate further. But thanks for this now!
:no_upscale():strip_icc():strip_exif()/f/image/iUeQ0FJsrDoNXlyDDCRBywXK.jpg?f=user_large){kind=link}