attribute encoder activationConditionRef

[Liam Hoekenga]

I was reading through the v3 documentation when I stumbled across this...

https://wiki.shibboleth.net/confluence/display/IDP30/AttributeEncoderPluginConfiguration#AttributeEncoderPluginConfiguration-activationConditionRef

"Typically this is useful to tie a specific encoding to a particular
RelyingParty (for those RPs that require non-standard forms), and avoids
the need to define extraneous attributes for that purpose."

I'm considering using this to reduce the number of attribute definitions we
have by adding SP specific encoders with with activationConditionsRefs in
them.  We have 8+ definitions for our university ID number because every SP
that wants it, wants it called something else.

My question is whether it's possible to structure the activation conditions
in something like a switch / if-else if-else statement.   i.e.  "If you're
not one of the SPs that needs an alternate encoder for this attribute, use
the default encoder".

Otherwise, I guess I could reduce 8+ to like... 2 - e.g. "employeeNumber"
(which only has the default) and "employeeNumberAlt" (which only has the
alternate encoders)... or continue to have separate attribute definitions
for each version of the attribute that requires it's own encoder.

Is there a best practice, or is this totally an issue of personal
preference?

Liam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20151111/f590e8bb/attachment-0001.html>