meta attributes (was: IdPv3 - eduPersonTargetedID - How to define and release this attribute?)
cantor.2 at osu.edu
Tue Apr 5 09:52:03 EDT 2016
> I don’t think they need to be interchangeable or identical for there to be
> value here. I want a sufficient schematic and semantic definition, and I want
> a set of operations to execute on those definitions to massage my data to a
> point where I can interoperate with the service provider.
And I don't think that's possible.
> If someone has already written an attribute resolver template that can be
> used with a particularly ornery SP, I want a copy of it to work from. If that has
> already been done by an IdaaS vendor, I’m a new customer. If that were
> distributed by the federation...
That's documentation. There is nothing to any of that but simple technical documentation that nobody can be bothered to write. And there are no such templates. Sources of attributes are a site-specific problem. You would be horrified by my resolver configuration and it would make no sense to you.
> I’ve seen software do that all day, under the names of attribute resolution
> and attribute mapping. Same story, different locus of definition.
Except it's not automated, those are produced by humans for a specific local need.
More information about the users