I’m not sure if this is an implementation error on my side or if this is a bug in the SSO implementation of Discourse. Users having a plus-extension in the local part of their e-mail address got an error since Discourse interpretes the plus sign as space. Following Setup DiscourseConnect - Officia…

[imagen] thabbs: base64_encode($nonce. You need "nonce=" . $nonce. there…

This is already there and was not the reason for my request. ( $nonce = base64_decode($sso); # starts with nonce=... )

A little late, I know. But in case anyone else runs into this problem. [imagen] thabbs: Following Official Single-Sign-On for Discourse (sso) I must not urlencode the payload before encoding it to base64 In fact we should urlencode the payload before base64 encoding. Our wordpress plugin an…

SSO y direcciones de correo electrónico con un signo más

Soporte

sam (Sam Saffron) 2 Octubre, 2018 01:30 2

You need "nonce=" . $nonce. there…

Tema		Respuestas	Vistas
Registration email address special characters Support	2	528	16 Agosto 2021
Watch out for double url encoding of SSO payload SSO	0	1586	28 Julio 2019
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	148	27 Julio 2026
Implementing SSO, nonce immediately expires Support	2	2153	2 Octubre 2019
SSO - "There is a problem with your account. Please contact the site's administrator." SSO	16	4958	18 Marzo 2019

SSO y direcciones de correo electrónico con un signo más

Temas relacionados