Content settings not applied when using SAMLDS SessionInitiator
Basics
Technical
Logistics
Basics
Technical
Logistics
Description
If you're using a SessionInitiator of the type SAMLDS, the content settings provided through the RequestMap or Apache configuration aren't applied to the resource.
As I speculated, actually processing request settings based on the target from within the DS handler is impossible, because the settings can be supplied via Apache and those data structures aren't in place when the actual request comes into the handler.
Only fix will be to pass them on the query string in the return URL to the DS.
Scott Cantor
August 19, 2010 at 12:28 PM
This might be obvious, but the workaround for now is probably to define a dedicated SessionInitiator with the properties you want, and then use requireSessionWith to reference that for the resources affected.
If you're using a SessionInitiator of the type SAMLDS, the content settings provided through the RequestMap or Apache configuration aren't applied to the resource.
The issue has been discussed at:
http://groups.google.com/group/shibboleth-users/browse_thread/thread/6b66d69409509a79#
Ideally, as Scott suggested, the SP should process all content settings based on the target resource, even when using the SAMLDS SessionInitiator.