<div dir="ltr"><div><div><div><div><div><div><div><div><div><div>Hi,<br><br></div>First of all thanks to everyone who worked on the 2.4.0 release, good work.<br><br></div>I am reading <a href="https://wiki.shibboleth.net/confluence/display/SHIB2/IdPEnableSLO">https://wiki.shibboleth.net/confluence/display/SHIB2/IdPEnableSLO</a> about the SLO support in 2.4.0, and have some questions.<br>
<br></div>1. Just to double confirm that IdP will terminate the session associated with the SP that send the logout request, and leave other SPs unchanged. How about the following scenario:<br></div> a. In one browser, I logged in as user1 for SP1 and SP2.<br>
</div> b. I click logout from SP1. New user1 in SP1 is logged out, but user1 in SP2 still loggs in, right?<br></div> c. What if I try to access SP1 in the same browser, will IdP prompt login screen? I guess yes, then can I login as a different user same user2 for SP1?<br>
</div> d. In the end, in one browser, user2 logged in SP1, and user2 logged in SP2, is that correct?<br><br></div>2. In Local logout section, I see "a direct non-SAML request", can you tell me what kind of request is that?<br>
<br>3. I am still not very clear what's different between Local and SAML logout in terms of session management on IdP side, I know that in SAML logout, it will terminate the session associated with this SP, and how about Local logout? I see "the IdP locates an active session based on the client's cookie and terminates it.", but what are the differences between these two sessions?<br>
<br></div>Please correct me if there is any misunderstanding.<br><br><br></div>Thanks,<br><div><div><div><div><div><div><div><div><div><div><div><div><div>Yaowen</div>
</div></div></div></div></div></div></div></div></div></div></div></div></div>