SPs with limitations on attributes they accept

[Kevin Foote]

On Jan 23, 2014, at 10:06 AM, Rawlinson, Philip (rawlinpa) <RAWLINPA at UCMAIL.UC.EDU> wrote:

> We have a couple of external SPs asking for values from our IdP, but they can only accept specific attributes. We have these values defined in custom attributes specific to our organization which they will not accept. One specific example is we have a custom attribute for the "college number" a student is in. The SP suggested we put this value into ou, but we already define that with different data.
>  
> 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?

Yes the attribute-resolver and attribute-filter are very flexible. As long as you have the raw attribute pulled in you can encode and release to what ever your RP wants per RP.

<https://wiki.shibboleth.net/confluence/display/SHIB2/IdPAddAttribute>

<https://wiki.shibboleth.net/confluence/display/SHIB2/IdPAddAttributeFilter>

This same topic has come up in the past 2 months or so on list .. please take a look at the archives.

--------
thanks
 kevin.foote