ePTID and ComputedId Persistence After IdP 3.3 -> 3.4 Upgrade
cantor.2 at osu.edu
Mon Feb 3 15:21:30 EST 2020
> I’ll switch to using the InputDataConnector within the DataConnector definition
I may have overlooked the full scope of what you were doing, so if you're more explicit about exactly which syntaxes you're needing to maintain support for, I can probably be more specific about the "advisable" way to do them all.
The one that's really "please stop doing this" is the embedding of a NameID inside an AttributeValue, using those XMLObject AttributeEncoders, but that's not really going away, it's just a bad idea.
Also, the property-driven persistent NameID code will produce the same computed values as the ComputedId connector will, given the same salt and encodings, and all of the options supported on one will be (in V4) properly supported on the other.
More information about the users