Opportunity ledger / Dossier O-2062
Recurring need documented in 1 independent public source item.
First seen 2026-07-10 · Last updated 2026-08-06 · Recalculated daily
Trend factor ×0.5, capped at 2.0.
Post title: OIDC SSO login fails with non-RS256 id_token signing algorithms (e.g. Logto's ES384): "unexpected JWT alg received, expected RS256"
Twenty should accept an ID token signed with whatever algorithm the issuer advertises in its OIDC discovery metadata, not only RS256.
What this evidence does not show yet
Only one independent item so far. One voice is a signal, not evidence of recurrence — treat this as a lead to investigate, not a validated need.
To reach Corroborated we still need:
No first-hand payment statement is on record here, so this page carries no pricing suggestion. A price with no payment evidence behind it is a guess wearing a number.
Follow how this opportunity evolves
Every item traceable · free · we email you only when this market actually changes
Scoring summary
Evidence confidence = strength × evidence volume × source diversity × payment × competition × trend × 10. Counts use independent content items; only first-hand pain, current spend, explicit willingness to pay and concrete feature requests affect the score. Repeated posts by one author are discounted. Scoring and status changes follow deterministic rules.
“Payment-backed” means first-hand payment evidence exists in the record. It does not mean the business is worth building. “Fading” is a recency tag shown alongside any evidence level, not a lower level. Read the full methodology.