Proxy IdP non-standard attribute names

[Cantor, Scott]

On 10/8/20, 5:00 PM, "users on behalf of Mak, Steve" <users-bounces at shibboleth.net on behalf of makst at upenn.edu> wrote:

>    For receiving the proxy attributes, if the proxy attributes have non-standard formal names (not matching anything in
> eduPerson.xml do I have to define these in Transcoding rules if I'm using v4 with a v3 resolver style syntax, or can I
> simply define these non-standard attributes in AttributeEncoders in the resolver?

Defining them as encoders is awkward (which is why we dumped it) but it works. The rules it translates them into are logged when the Registry service starts up or reloads so it's possible to scan them and catch mistakes.

You don't have to convert everything just to drop a few custom rules in, so I really wouldn't use encoders. The only thing upgrading blocks is the loading of all the predefined rules, it still searches the custom directory for one-off files.

-- Scott