Returning failure for isPassive

[Cantor, Scott]

On 10/29/12 2:47 PM, "Christopher Bongaarts" <cab at umn.edu> wrote:

>If an SP requests isPassive, and my login handler determines that it
>cannot proceed without user interaction, what should it do (codewise)?

Create an AuthenticationException and set that attribute before returning
to the engine. I believe there's a dedicated exception type to signal that
that's the problem. My login handler has some code that does it, though I
haven't tested that aspect.

>Tried looking around the IdP source but didn't see any examples there.

Everything in the IdP built-in just lets the selection machinery handle
it, so there's code in the engine class for selecting a login handler that
probably illustrates the exception type to use.

-- Scott