La sincronizzazione SSO lato server rifiuta payload validi con 422 "Errore di accesso" quando il base64 contiene un `+` (scatenato da `~` nei campi sincronizzati)

zogstrip · 24 Luglio 2026, 2:04pm

Grazie per il report @sweetbeems Verrà corretto da

github.com/discourse/discourse

FIX: Preserve "+" in server-side sync_sso payloads (#42024)

main ← fix-sync-sso-plus-double-decode

merged 02:28PM - 24 Jul 26 UTC

ZogStriP

+51 -19

Previously, `sync_sso` rebuilt its query string from the already form-decoded `p…arams[:sso]` and let `DiscourseConnect.parse` decode it a second time, so any literal `+` in the base64 payload became a space and a correctly-signed request was rejected with a generic 422 "Login Error". This change rebuilds the query with `Rack::Utils.build_query` — the exact inverse of the `parse_query` the parser runs — so the payload is decoded exactly once. The second commit applies the same reasoning to `CookedPostProcessor#remove_user_ids`, which rebuilt link query strings by hand and corrupted encoded values (e.g. `%26`) when stripping the `u=` param. Reported at https://meta.discourse.org/t/407426.

Argomento		Risposte	Visualizzazioni
Issues with SSO and '~' character Support	8	187	Febbraio 20, 2025
Watch out for double url encoding of SSO payload SSO	0	1567	Luglio 28, 2019
SSO and e-mail addresses having a plus sign Support	3	2116	Aprile 14, 2021
Registration email address special characters Support	2	500	Agosto 16, 2021
Sso login error when return_sso_url is blank Bug	2	1338	Agosto 15, 2016

La sincronizzazione SSO lato server rifiuta payload validi con 422 "Errore di accesso" quando il base64 contiene un `+` (scatenato da `~` nei campi sincronizzati)

Argomenti correlati