SPs with limitations on attributes they accept

[Peter Schober]

* Rawlinson, Philip (rawlinpa) <RAWLINPA at UCMAIL.UC.EDU> [2014-01-23 19:09]:
> Does anyone have suggestions on how to get data like this to SPs
> that will only accept it in specific fields? I am considering
> putting the "college number" into a field they do accept that is
> likely never to be used by another SP, but that is a last resort. Is
> it possible to use a "Script Attribute Definition" to change the
> values of an attribute like ou, but only for specific SPs?

Instead of misusing arbitrary other attributes, the common way to do
this is to define new attributes in the IDP's resolver which depend
(sourceAttributeID, Dependency) on the local attribute you want to use
(here: the attribute that contains your "college number") and add
encoders that will name them the way the SP expects.
Give this attribute definition an id value that indicates that this is
your collegge number specific for that vendor
("collegeNumber4FooVendor").
Then in your attribute filter you only release this custom attribute
(via its id) to this vendor. That way nothing else changes wrt your
(or your other SPs') uses of your college number and ou attribute.
-peter