custom flow problems

Jim Fox fox at washington.edu
Fri Jan 16 18:28:54 EST 2015



OK, got it all straight now.  Web-flow can be confusing in places.

Thanks for the help.

Jim


On Fri, 16 Jan 2015, Cantor, Scott wrote:

> Date: Fri, 16 Jan 2015 14:41:39
> From: "Cantor, Scott" <cantor.2 at osu.edu>
> To: Shib Dev <dev at shibboleth.net>
> Reply-To: Shib Dev <dev at shibboleth.net>
> Subject: RE: custom flow problems
> 
>> When it does not work, remoteuserplus in flows/authn, I see this flow:
>>
>>    Calling subflow 'authn' with input map['calledAsSubflow' -> true]
>>    Entering state 'RemoteUserActionChooser' of flow 'authn'
>>    ...
>>
>> It is going directly the the remoteuserplus flow, skipping authn-flow entirely.
>> Thus PopulateAuthenticationContext never gets called.
>
> I think you're misnaming your flow and overriding the whole thing.
>
>> So, for some reason the auth-flow now its bean definitions ever get loaded
>> when I run a flow out of the local flows directory.
>
> I think you've replaced the authentication subflow with a custom login subflow, which is bad. What did you put into conf/flows/?
>
> If you want to create something called authn/remoteuserplus, you need a flow definition in /conf/flows/authn/remoteuserplus/remoteuserplus-flow.xml
>
> If it's named anything else or put into any other place, it won't work. The beans file is up to you because it's imported into your flow file, but the convention is the obvious one.
>
> -- Scott
>
> -- 
> To unsubscribe from this list send an email to dev-unsubscribe at shibboleth.net
>


More information about the dev mailing list