Silently try more then one login handler with UnsolicitedSSO

[Cantor, Scott]

On 4/22/13 4:42 PM, "Douglas E. Engert" <deengert at anl.gov> wrote:

>PreviousSession always appears to be tried first. In other words
>is there a way to have additional login handlers silently tried too?

PreviousSession isn't in any meaningful sense a login handler. It's
handled out of band with special code. It shouldn't be thought of except
as a "flag" for using the built-in SSO support or not.

Separating that from the conversation, there is no way to run multiple
handlers. Doing so means writing your own and turning what was a login
handler into something internal to your own handler.

>Is there anyway to pass additional parameters to UnsolicitedSSO
>to tell it to request a specific login handler(s)?

Not explicitly. I believe it will honor the default method set for the
relying party corresponding to the providerId parameter.

You could also create your own SAML 2 request message with an explicit
RequestedAuthnContext element corresponding to the handler to run.

-- Scott