Michael.Jones at microsoft.com
Wed Nov 14 23:35:18 UTC 2018
I agree that this should follow the same pattern as the redirect_uri - https, path permitted, query parameters permitted and preserved, fragment not permitted.
Filip Skokan also pointed out that there is likewise no description of the syntax of initiate_login_uri. My sense is that should also be the same.
From: Openid-specs-ab <openid-specs-ab-bounces at lists.openid.net> On Behalf Of Roland Hedberg via Openid-specs-ab
Sent: Wednesday, November 14, 2018 7:14 AM
To: <openid-specs-ab at lists.openid.net> <openid-specs-ab at lists.openid.net>
Cc: Roland Hedberg <roland at catalogix.se>
Subject: [Openid-specs-ab] post_logout_redirect_uri
post_logout_redirect_uri are defined in https://openid.net/specs/openid-connect-session-1_0.html
and refreed to in https://openid.net/specs/openid-connect-frontchannel-1_0.html.
In neither of these documents are there any specification of what a post_logout_redirect_uri is allowed to look like.
backchannel_logout_uri in https://openid.net/specs/openid-connect-backchannel-1_0.html is defined as:
”The back-channel logout URI MUST be an absolute URI as defined by Section 4.3 of [RFC3986].
The back-channel logout URI MAY include an application/x-www-form-urlencoded formatted query component, per Section 3.4 of [RFC3986], which MUST be retained when adding additional query parameters.
The back-channel logout URI MUST NOT include a fragment component.”
The same goes for frontchannel_logout_uri in https://openid.net/specs/openid-connect-frontchannel-1_0.html
I would expect the same rule to apply to post_logout_redirect_uri.
"Education is the path from cocky ignorance to miserable uncertainty.” - Mark Twain
Openid-specs-ab mailing list
Openid-specs-ab at lists.openid.net
More information about the Openid-specs-ab