Hi everyone, So recently I discovered that if I inclue ‘~’ in a user’s bios, I get a base64decode error from Discourse. It can handle all sorts of other problematic characters just fine (spaces, =, %, &) but not ~ for some reason. Anyone else encounter this issue? My first thought is that perhaps…

Upon further investigation, I was indeed encoding it wrong. Here is what I ended up with, for posterity: return_payload = base64.b64encode(parse.urlencode(kwargs).encode("utf-8")) h = hmac.new(secret.encode("utf-8"), return_payload, digestmod=hashlib.sha256) resp = requests.post( ".../admin…

Heh I guess that’s a reasonable question. I run a multilingual forum and in other cultures ‘~’ is frequently used. As an example, in Korean, it’s often used at the end to soften your tone, like ‘If you have any questions, let me know~’

So this is a bug report and not a support request?

Is it? A bug is something that is done, but doesn’t work. This is more like question ”is it done or not” and then it’s more Contribute > Feature if not a support question.

[image] Thomas Kalka: So this is a bug report and not a support request? [image] Jakke Flemming: Is it? A bug is something that is done, but doesn’t work. This is more like question ”is it done or not” and then it’s more #feature::category if not a support question. Yeah I think Bug is…

I think it is a bug (provided we can repro it)

[image] sweetbeems: Here is my python implementation of the encoding: return_payload = base64.urlsafe_b64encode(parse.urlencode(params).encode()) It looks like urlsafe_b64encode replaces some characters in the base64 encoding. From the docs : Encode bytes-like object s using the URL- and fi…

Issues with SSO and '~' character

Support

Jagster (Jakke Flemming) February 11, 2025, 6:51am 2

It propably should be fixed, but that question is above my paygrade and skills. But out of pure practical curiosity: why someone would use a tilde in a bio?

Topic		Replies	Views
Server-side sync_sso rejects valid payloads with 422 "Login Error" when the base64 contains a `+` (triggered by `~` in synced fields) Bug sso , fixed	2	72	July 27, 2026
SSO and e-mail addresses having a plus sign Support	3	2118	April 14, 2021
Watch out for double url encoding of SSO payload SSO	0	1567	July 28, 2019
Registration email address special characters Support	2	501	August 16, 2021
Unicode usernames Development rest-api	28	1734	November 29, 2024

Issues with SSO and '~' character

Related topics