I am looking at upgrading our Virtual Home IdP to IdP 3.2.1.
We use a MySQL database as the backend.
I have learned from the release notes that IdP 3.2.1 RelationalDatabaseConnector returns EmptyAttributeValue instances in place of MySQL NULLs. In IdP 2.4.x, these were silently discarded and the attributes had an empty set of values.
The consent module in 3.2.1 does not properly filter out the EmptyAttributeValues and displays such attributes on the consent screen - I get this (the attribute names come from resolver:DisplayName elements I have in my attribute-resolver.xml):
I think the correct behavior would be to not display attributes that only have empty values (and do not get included in the AttributeStatement).