Change the "name=" value for the UID attribute definition for specific entityIDs
Joseph.Fischetti at marist.edu
Thu Oct 5 11:11:04 EDT 2017
> Yes, that's the case I mentioned that may or may not be what you want but might influence
> the value of bothering with doing it like this. Most of the time that SP won't care though.
Regardless of whether or not it's necessary in *this* particular case, it's still valuable to know about the functionality and how/why it works.
On the topic of maintenance, it's an easier process to simply define a new attribute and release that attribute only to certain SP(s), as the original poster was trying to accomplish. It also doesn't require a restart since resolver and filter can be reloaded. As long as the attribute-resolver and attribute-filter configurations are well documented, fewer files have been touched in the process. Using the activation condition, I've created an additional file and made changes to services.xml (which up until this point, was default).
On the other hand, adding a 'random' attribute simply for one SP will add to the processing overhead when it comes to filtering attributes.
Linux System Administrator
More information about the users