- Only show me content:
- Unfiltered files: dynamically added content
- Filtered files: dynamically added content
- Clear filters
|Participant||Role||Time Spent||Comments||Latest Comment|
|Author & Moderator||2h||6||Extracted this to OPENAM-6776 for better tracking.|
|Reviewer - Complete||19m||4||Looks good.|
|Reviewer - Complete||28m|
|Reviewer - 72% reviewed||18m|
The main problem is that session upgrade triggers a session destroy for the old session and a new session is created during the upgrade. The solution for me was to introduce a new extension that SAML can utilize to ensure that during a session upgrade the cached data is relocated before IDPSessionListener would capture the destroy event and do its own cleanup job.
If the Saml2SessionUpgradeHandler code looks arbitrary, then that's because I've tried to look at IDPSessionListener and make sure that whatever IDPSessionListener would normally do can't happen during a session upgrade.
Issues Raised From Comments