[keycloak-dev] Inconsistency in handling null User attribute values: IdentityProviderMapper versus UserRepresentation

Alex Szczuczko aszczucz at redhat.com
Wed Jun 7 10:42:52 EDT 2017


My work on KEYCLOAK-4778 highlighted an inconsistency in User attribute value handling. When a IdentityProviderMapper accepts a user attribute, it seems (I haven't looked at all of them) they will drop (not import/store) those that have a null value. However, the REST API does something different. UserRepresentation (through StringListMapDeserializer) will convert null values to a String of "null".

Any objections to changing StringListMapDeserializer to also ignore null valued attributes? UserRepresentation is the only user of StringListMapDeserializer.


More information about the keycloak-dev mailing list