Additional params through ExternalAuthn LoginHandler

[snekse]

Thanks Scott.  Your last point is a good point.

I have a couple of follow up questions.

You state that "any information in the request to the IdP is accessible
from the login context via the API".  Looking at the
API, loginContext.getProperty seems to be the only thing that would make
sense of where I might pull request information. (1.) Would the original
request params be in here?

If I added a 'target' param to my /idp/profile/SAML2/Unsolicited/SSO
request, it seems like that gets saved off as the relayState for user later
when building the SAML message. I could embed the key param into the
relayState, but I wouldn't want to pass that to the SP.  (2.) Is there a
way to extract the relayState, then alter it for the duration of the
request?

As I slowly start drifting away from the "correct" solution... a filter
seems like an option.  Before the redirect, alter the redirect URL to
append the 'key' param.  Despite making my skin crawl, a hack solution is
better than no solution. (3.) Is there any technical reason you can think
of that would make this impossible?


#SadSadTears
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20140729/2ab5e5b3/attachment-0001.html