Experiments with command-line and web flow adaptor
Cantor, Scott
cantor.2 at osu.edu
Tue Apr 2 17:13:10 EDT 2013
I checked in some preliminary work so we can talk about it Friday or next
week. I tried to avoid much refactoring, but I had to adjust a few
existing IdP profile classes so that I could reuse some of the code along
with my new code, but the changes are small and some of it would drop out
if we actually commit to doing things this new way.
The non-Spring aware bits are in opensaml-messaging-api for now. I would
think they would go into a new opensaml-profile-api module if we kept them.
There's a new ProfileAction interface there, a copy of the
ProfileRequestContext class from the IdP, and an AbstractProfileAction
base class that mirrors the original one. Actions that are not
Spring-aware would inherit from that base. Actions that are Spring-aware
can currently inherit from that base and access Spring via a new
subcontext I created, or they could inherit from the existing
AbstractProfileAction as all the current ones do now. We can rationalize
that of course.
Finally, you can see the way the webflow and bean configs look with my
suggested design in the idp-attribute-cli project, in
src/main/resources/conf.
The webflows look exactly the same as before, only the flow-beans change
slightly.
The CLI app runs a flow with 2 Spring-aware and 1 Spring-nonware actions,
so both are illustrated.
This also demonstrates using a webflow without the web.
-- Scott
More information about the dev
mailing list