...
Other Examples
Non-Standard Naming
While I would strongly we advise against doing so, you will run into constrant pressure from vendors to support one-off Attribute names. When you agree to do that, you should understand that it won’t stop, and you will end up over time with dozens of these rules to maintain and a brittle configuration prone to problems. Standards exist for that reason.
...
This is merely an alternative approach to using an AttributeEncoder to do the same thing, just outside instead of inside the resolver configuration.
Metadata-Driven Naming 5.1
Yet another way to handle exception-based naming rules is with SAML metadata. Each set of transcoders for a protocol supports its own property for instructing the system to check for a metadata “tag” extension that carries values specifying naming rules specific to that SP. This approach only applies to encoding of data, not decoding. Refer to the protocol-specific transcoder topics linked above for the details and examples.