# Linkedin OIDC broken

**URL:** https://meta.discourse.org/t/linkedin-oidc-broken/377936
**Category:** Support
**Tags:** login, signup
**Created:** [August 8, 2025, 8:16pm UTC](https://meta.discourse.org/t/linkedin-oidc-broken/377936 "2025-08-08T20:16:57Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![haydenjames](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/haydenjames/32/255678_2.png) [@haydenjames](https://meta.discourse.org/u/haydenjames)
#### Post date: [August 8, 2025, 8:16pm UTC](https://meta.discourse.org/t/linkedin-oidc-broken/377936/1 "2025-08-08T20:16:57Z")

</div>

I was only able to find this locked thread:

> [@LinkedIn OIDC client secret not correctly validating new format](https://meta.discourse.org/t/linkedin-oidc-client-secret-not-correctly-validating-new-format/308016):
>
> [image] I have successfully created an application on linkedin, but when I try to copy client\_secret, I receive the following message. At the same time, the Callback url displays this message

I tried to regenerate the secret key:

 ![image](https://global.discourse-cdn.com/meta/original/4X/4/9/3/49379b593b5da1260b97f8d7a34f6006794bdd26.png)

But still get this error:

> linkedin\_oidc\_client\_secret: Value doesn’t match the required format.

 ![image](https://global.discourse-cdn.com/meta/original/4X/8/1/0/810e0a5536c406119a1b7464c3588493aed1e8a4.png)

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?

---

<div class="post-metadata">

### Author: ![haydenjames](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/haydenjames/32/255678_2.png) [@haydenjames](https://meta.discourse.org/u/haydenjames)
#### Post date: [August 9, 2025, 2:05pm UTC](https://meta.discourse.org/t/linkedin-oidc-broken/377936/2 "2025-08-09T14:05:08Z")

</div>

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:

![image](https://global.discourse-cdn.com/meta/original/4X/1/0/4/1042e74f77732122ffbce34560363dc853846eee.png)

So probably this needs to be [patched](https://github.com/discourse/discourse/pull/27028) again as that’s the more acceptable and safer solution.

---

<div class="post-metadata">

### Author: ![PCPal](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pcpal/32/455064_2.png) [@PCPal](https://meta.discourse.org/u/PCPal)
#### Post date: [August 10, 2025, 1:47pm UTC](https://meta.discourse.org/t/linkedin-oidc-broken/377936/3 "2025-08-10T13:47:02Z")

</div>

Ah! Thanks for sharing. I recently moved my forum to [this very professional setup](https://tweakers.net/i/4BtHd680Ki1Gaf7Z7hy0MZx564c=/fit-in/4920x3264/filters:max_bytes(3145728):no_upscale():strip_icc():strip_exif()/f/image/iUeQ0FJsrDoNXlyDDCRBywXK.jpg?f=user_large), 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!