IDP3 authn intercept question

[O'Dowd, Josh]

>Alternatively you could build a login flow that just calls the password flow, and then supplements processing after a proceed result from it, that's a fairly simple thing to do.

This is an 'I just quickly read some available docs' guess, but are we talking about adding a new bean to conf/authn/general-authn.xml where the ID might be 'authn/my-password' and a parent that is 'shibboleth.AuthenticationFlow' to get things started?  Am I on the right track?

-Josh

-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Wednesday, September 30, 2015 12:40 PM
To: Shib Users
Subject: Re: IDP3 authn intercept question

On 9/30/15, 2:36 PM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:

>I think you really should look at hooking, or if necessary replacing, the login flow itself and prevent it from producing a successful result in the first place.

Alternatively you could build a login flow that just calls the password flow, and then supplements processing after a proceed result from it, that's a fairly simple thing to do.

-- Scott

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