[Openid-specs-ab] OIDC Session Management and third party cookie blocking

[Mischa Salle]

On Tue, Aug 09, 2022 at 06:39:27PM +0000, Nicole Roy via Openid-specs-ab wrote:
> My concern would be that a browser employing “Intelligent Tracking Prevention” would see the POST of the SID as tracking and prevent it. Of course, doing so breaks all sorts of other things, but the browser people don’t seem to care about that at the moment.

probably would have the same problems with "nonce" and "state" then?
Plus makes one wonder whether these three could not have been a single
parameter?

Mischa

> > On Aug 2, 2022, at 4:30 PM, Jake Feasel via Openid-specs-ab <openid-specs-ab at lists.openid.net> wrote:
> > 
> > This topic has been raised before, but based on the traffic from this list it seems to not be going anywhere. I would like to revive it.
> > 
> > I had a quick talk at Identiverse this year covering the OIDC Session Management draft spec, in particular my take on the upcoming "Cookiepocalypse" and how it will render the current draft completely obsolete. You can see my slides here: https://docs.google.com/presentation/d/1uU3KvK6ayTpjB2OEmrSqQnUdJDPSdfxxetJrks1czvI/edit#slide=id.g11aa5093f19_0_63 <https://docs.google.com/presentation/d/1uU3KvK6ayTpjB2OEmrSqQnUdJDPSdfxxetJrks1czvI/edit#slide=id.g11aa5093f19_0_63>
> > 
> 
> [snip]
> 
> > The OP will include the "sid" claim (as defined in the Front and Back-channel logout drafts) as a claim in the id_token used in an auth_code grant. This "sid" value will be included in a POST request to the "token" endpoint on the OP on a periodic basis (likely prompted from user activity within the RP). It would like something like so (note the absence of a cookie in this request):
> > 
> >   POST /token HTTP/1.1
> >   Host: server.example.com <http://server.example.com/>
> >   Content-Type: application/x-www-form-urlencoded
> >   Authorization: Basic czZCaGRSa3F0MzpnWDFmQmF0M2JW
> > 
> >   grant_type=session_check&sid=1234xyz
> > 
> > The response code from this could be a 401 if the sid is not associated with a valid OP session, or 200 if it is. The response body in the case of a 200 could include a new id_token with updated session claims (to provide better context for when the session expires or if other important details about the session change).
> > 
> 
> [snip]
> 



> _______________________________________________
> Openid-specs-ab mailing list
> Openid-specs-ab at lists.openid.net
> https://lists.openid.net/mailman/listinfo/openid-specs-ab


-- 
Nikhef                      Room  1.14
Science Park 110            Tel.  +31-6-4681 2202
1098 XG Amsterdam           Fax   +31-20-592 5155
The Netherlands             Email msalle at nikhef.nl
  __ .. ... _._. .... ._  ... ._ ._.. ._.. .._..