ProfileRequestContext accessibility outside flow actions

[Marvin Addison]

I have an arguably crazy use case for LDAP authn that I'll sketch out
briefly. We want the ability to set the SASL authorization ID based on
artifacts in the request like relying party ID and principal ID. Daniel and
I discussed an implementation strategy and it looks like an ldaptive
Activator component is the way to go. It's a pretty straightforward
implementation except for one obstacle: need to access the context tree
from a component way outside a flow execution context.

It's pretty easy to imagine a lookup function of
Function<HttpServletRequest, String> that would leverage
the shibboleth.HttpServletRequest component to get at the request, and if
the PRC were accessible as, say, a request attribute, it would be trivial
to get at the needed subcontexts. I would like to propose that a simple
one-liner be added to InitializeProfileRequestContext to support this case:

((HttpServletRequest)
springRequestContext.getExternalContext().getNativeRequest()).setAttribute(ProfileRequestContext.BINDING_KEY,
prc);

Seems generally useful and easy to implement. Thoughts?

M
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20150813/3fbf6646/attachment-0001.html>