Subflow input mappings are lost in transitions
Cantor, Scott
cantor.2 at osu.edu
Mon Aug 24 12:22:28 EDT 2015
On 8/24/15, 12:18 PM, "dev on behalf of Misagh Moayyed" <dev-bounces at shibboleth.net on behalf of mmoayyed at unicon.net> wrote:
>Even if this were an actual issue, I very much doubt it could be solved
>via pure XML config. You'd have to rewrite the entire flow declaration via
>Java beans or something to be able to handle that type of dynamic!
Right, our I/O interface is the tree. Lack of documentation aside, our subflows today all have specific calling conventions regarding what has to be in the tree (and as we see in the case of attribute release, there's an accidental SAMLism stuck in at least one of them that we have to remove).
-- Scott
More information about the dev
mailing list