[JIRA] Resolved: (SSPCPP-400) NameID lookup for logout ignores logical SP boundaries
Scott Cantor (JIRA)
noreply at shibboleth.net
Thu Mar 15 17:01:16 GMT 2012
[ https://issues.shibboleth.net/jira/browse/SSPCPP-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Cantor resolved SSPCPP-400.
---------------------------------
Resolution: Fixed
http://svn.shibboleth.net/view/cpp-sp?view=rev&rev=3592
The expiration of the indexing is built-in, so there's no concern over leaving them in place.
> NameID lookup for logout ignores logical SP boundaries
> ------------------------------------------------------
>
> Key: SSPCPP-400
> URL: https://issues.shibboleth.net/jira/browse/SSPCPP-400
> Project: Shibboleth SP - C++
> Issue Type: Bug
> Components: SAML 2.0 Logout
> Affects Versions: 2.4, 2.4.1, 2.4.2, 2.4.3
> Reporter: Scott Cantor
> Assignee: Scott Cantor
> Fix For: 2.5
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> The cache of NameID->Session mappings for logout lookup don't recognize that some sessions are bound to different SP entityID containers, which causes the IdP to issue requests for logout to those entityIDs after the initial request and causes a failure since the sessions are already gone.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the commits
mailing list