You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is possible to whitelist properties for serialization using a FIlterProvider. Whitelisting is more secure than blacklisting and a similar approach should be available for deserialization.
The text was updated successfully, but these errors were encountered:
Makes sense. The main challenge with all changes to deserialization is that number of code paths is much higher for BeanDeserializer than BeanSerializer. But hopefully this can be implemented at some point.
I think this might be covered by #1296, if and when that gets implemented. Mechanism would be different. However, since filters are not used for deserialization, I think I'll close this in favor of the annotation based variant, since adding support for filters for deserialization is not likely to be implemented in near term.
It is possible to whitelist properties for serialization using a FIlterProvider. Whitelisting is more secure than blacklisting and a similar approach should be available for deserialization.
The text was updated successfully, but these errors were encountered: