Need some authn config strategy help.

Cantor, Scott cantor.2 at osu.edu
Fri Jul 24 13:22:14 EDT 2015


On 7/24/15, 12:39 PM, "users on behalf of O'Dowd, Josh" <users-bounces at shibboleth.net on behalf of Josh.O'Dowd at mso.umt.edu> wrote:

>I think I may have found the intended solution in the config wiki…   Maybe you can confirm…
> 
>To extend/customize the flow, I can implement my own flows in the /flows/authn/conditions directory by adding customized directory/sub-flow.xml and mapping the condition to the associated classified error.

Yes, but I don't know if that will do everything you need to do or not. I believe you can abort the login by signaling a non-proceed event from within one of those subflows, in which case that part at least provides a degree of control. I don't know for certain if it will.

But yes, I built in a whole layer of subflow signaling inside there that hopefully avoids the need to actually modify or duplicate the password flow.

>Can there be any consideration in future iterations of IDP3 to allow for custom bean inclusion to the incoming request model for views?

I thought Tom basically figured out a way to get that work using web.xml (which you probably could do now) but I haven't reviewed it.

-- Scott



More information about the users mailing list