extending/modifying expiring password flow and LDAP properties

[Scott Koranda]

> > Without it I naively do not see how beans defined as part of the
> > expiring-password-flow can be made aware of beans known to the
> > password-authn-flow since there is no parent/child context relationship.
> 
> They wouldn't be, but beans can be defined above and inherited into
> both. None of the existing beans were really intended to be shared in
> that way, but using aliases and other tricks can certainly make them
> so. I just don't know any of the interdependencies of the LDAP
> machinery so I assumed there might be a large amount of displacement,
> which makes it possible but somewhat impractical. With JDBC, it's
> typically a pretty self-contained object.

Oh of course. I could move the necessary pool beans into global.xml,
perhaps with some aliasing, and then just reference them in
ldap-authn-config.xml and expiring-password-beans.xml.

I will try that next.

Thanks,

Scott K