custom flow problems

[Cantor, Scott]

> 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