metadata-driven attribute definition

Peter Schober peter.schober at
Mon Jul 15 08:48:02 EDT 2019

* Peter Schober <peter.schober at> [2019-07-15 14:31]:
> * Joshua Dachman <jdachman at> [2019-07-14 23:00]:
> > The idea is to be metadata-driven here. Yes, the same can currently be
> > achieved through addition of tags in attribute-resolver.xml, but then every
> > time an SP desires a custom mapping it must be added there rather than in
> > the SP's metadata.
> So far I found adding another AttributeEncoder with a relyingParties
> XML attribute to be sufficient and easy to do.

Oh wait, you didn't ask about one-off attribute names in metadata (for
which a differing encoder would be relevant) but you wanted to use a
different InputAttributeDefinition for a given standard attribute
depending on the SP entity?

I don't think I ever had to handle that case and certainly "metadata
ftw!" wouldn't have been my initial reaction.


More information about the users mailing list