[Openid-specs-ab] FW: OpenID Connection session management: determining which RP is initiating the logout

Mike Jones Michael.Jones at microsoft.com
Wed Nov 20 04:58:00 UTC 2013


This sounds like something we should add to the security considerations.

From: John Bradley [mailto:ve7jtb at ve7jtb.com]
Sent: Tuesday, November 19, 2013 6:54 PM
To: Mike Jones
Cc: openid-specs-ab at lists.openid.net
Subject: Re: [Openid-specs-ab] FW: OpenID Connection session management: determining which RP is initiating the logout

The id_token hint is the only way to know.  Sending it is a SHOULD so unless there is some good reason not to send it,  it should be included.

If I were a IdP I would treat any logout   Requests without it as possible denial of service attacks requiring additional confirmation from the user.

Sent from my iPhone

On Nov 19, 2013, at 9:32 PM, Mike Jones <Michael.Jones at microsoft.com<mailto:Michael.Jones at microsoft.com>> wrote:
A Microsoft developer asked this question.  Thoughts?

Mike,
                I’ve been reviewing our implementation of OpenID Connect session management.  In the RP-initiated logout mechanism, the STS is required to validate that, if the post_logout_redirect_uri is supplied, that it match one of the values registered for that RP.  However, what’s not clear from the OpenID Connect Session Management spec is how the STS can determine which RP sent the logout request (so the STS can determine which RP’s info to use to validate the post_logout_redirect_uri).  There does not seem to be any required parameter in the logout request that would specify the RP sending it.  The closest is the id_token_hint (i.e., the STS can look inside the token to see its audience), but the id_token_hint is recommended, not required (and really seems intended for determining the user identity, not the RP identity).
                What is the expected means by which an STS can determine which RP is initiating the logout?

5.  RP-Initiated Logout
An RP can notify the OP that the End-User has logged out of the site, and might want to log out of the OP as well. In this case, the RP, after having logged the End-User out of the RP, redirects the End-User's User-Agent to the OP's logout endpoint URL. This URL is normally obtained via the end_session_endpoint element of the OP's Discovery response, or MAY be learned via other mechanisms.
This specification also defines the following parameters that are passed as query parameters in the logout request:
id_token_hint
RECOMMENDED. Previously issued ID Token passed to the logout endpoint as a hint about the End-User's current authenticated session with the Client. This is used as an indication of the identity of the End-User that the RP is requesting be logged out by the OP. The OP need not be listed as an audience of the ID Token when it is used as an id_token_hint value.
post_logout_redirect_uri
OPTIONAL. URL to which the RP is requesting that the End-User's User-Agent be redirected after a logout has been performed. The value MUST have been previously registered with the OP, either using the post_logout_redirect_uris Registration parameter or via another mechanism. If supplied, the OP SHOULD honor this request following the logout.

_______________________________________________
Openid-specs-ab mailing list
Openid-specs-ab at lists.openid.net<mailto:Openid-specs-ab at lists.openid.net>
http://lists.openid.net/mailman/listinfo/openid-specs-ab
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20131120/02edb05c/attachment.html>


More information about the Openid-specs-ab mailing list