서버 측 sync_sso가 base64에 `+`가 포함되면(동기화 필드에 `~`가 있을 때 발생) 유효한 페이로드를 422 "Login Error"로 거부함

zogstrip · 7월 24, 2026, 2:04오후

리포트 감사합니다 @sweetbeems 다음 링크에서 수정됩니다.

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.

글		댓글	조회수
Issues with SSO and '~' character Support	8	225	2월 20, 2025
Watch out for double url encoding of SSO payload SSO	0	1580	7월 28, 2019
SSO and e-mail addresses having a plus sign Support	3	2145	4월 14, 2021
Registration email address special characters Support	2	515	8월 16, 2021
Sso login error when return_sso_url is blank Bug	2	1351	8월 15, 2016

서버 측 sync_sso가 base64에 `+`가 포함되면(동기화 필드에 `~`가 있을 때 발생) 유효한 페이로드를 422 "Login Error"로 거부함

Related topics