当 base64 包含 `+`（由同步字段中的 `~` 触发）时，服务端 sync_sso 会拒绝有效负载并返回 422 “登录错误”

zogstrip · 2026 年7 月 24 日 14: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	187	2025 年2 月 20 日
Watch out for double url encoding of SSO payload SSO	0	1567	2019 年7 月 28 日
SSO and e-mail addresses having a plus sign Support	3	2116	2021 年4 月 14 日
Registration email address special characters Support	2	500	2021 年8 月 16 日
Sso login error when return_sso_url is blank Bug	2	1338	2016 年8 月 15 日

当 base64 包含 `+`（由同步字段中的 `~` 触发）时，服务端 sync_sso 会拒绝有效负载并返回 422 “登录错误”

相关话题