[Openid-specs-ab] [EXTERNAL] OP logout tests: OP-Session-RpInitLogout

[Mike Jones]

Yeah, I'm having the same issue with OP-Session-RpInitLogout when testing the Session Management support on AAD V1.  Roland is looking into it.  (It may be an AAD bug, but we don't know yet.)

The OP is supposed to be using the iframes to trigger a logout via a state change message.

				-- Mike

-----Original Message-----
From: Openid-specs-ab <openid-specs-ab-bounces at lists.openid.net> On Behalf Of Vladimir Dzhuvinov via Openid-specs-ab
Sent: Thursday, November 28, 2019 12:05 PM
To: openid-specs-ab at lists.openid.net
Cc: Vladimir Dzhuvinov <vladimir at connect2id.com>
Subject: [EXTERNAL] [Openid-specs-ab] OP logout tests: OP-Session-RpInitLogout

First, our thanks to everyone for the new logout cert tests. It took us an hour to setup a server and run them, so if there are people still wondering whether to give them a try, there are 13 tests in total and it takes little time to cycle through them.

I have a question about OP-Session-RpInitLogout - the last one from the suite ("Uses RP initiated logout to end a Session at the OP. The RP uses session management to register the session state change").

What does this test actually do? After the IdP login screen the browser is directed to a page on the cert domain

> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fop.c
> ertification.openid.net%3A60533%2Fauthz_cb%3Fcode%3D-3YoTPwuXenTtrGbcb
> rdbw.Wx3k3trWIeht9FYf6hPIAg%26state%3DJQfN9tCIGgz5ErBp%26session_state
> %3D-D8nmOMzRg4EYddgM3xSZ14HRoYdhUZp9OEiaLUZF5s.lHXF6TaaBVCWL_-jaVQX_A&
> amp;data=02%7C01%7CMichael.Jones%40microsoft.com%7C29272e474bc34634725
> 108d7743f4a4a%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C63710568749
> 2732198&sdata=tZssQOXZheqA8LPo%2BSMciss2VAxAWGOc6jw%2BMzde1jg%3D&a
> mp;reserved=0

which displays the following message

> Session verification
>
> Checking that the session hasn't changed!

There was no further progress or redirection.

Going back to the test list displays the test icon as "The test has not been run yet" and there is no test information / debugging info to check what might have gone wrong.

Thanks,

Vladimir