Silently try more then one login handler with UnsolicitedSSO

[Douglas E. Engert]

On 4/22/2013 4:36 PM, Cantor, Scott wrote:
> 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.

OK, that looks interesting, and might just work for this one vendor
at least. I will have a look at that.

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

I will look at that too.

Thanks.

>
> -- Scott
>
>
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
>

-- 

  Douglas E. Engert  <DEEngert at anl.gov>
  Argonne National Laboratory
  9700 South Cass Avenue
  Argonne, Illinois  60439
  (630) 252-5444