# 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:** 1
**Showing post:** 2

<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.

---

_[View the full topic](https://meta.discourse.org/t/linkedin-oidc-broken/377936)._
