Attribute Mappers

[cgeorgilakis]

All attribute mappers supports list value.

1. If an Attribute Mapper has force Sync Mode Override, every time user logins user attribute value will be overiden with value IdP return ( or User Attribute removed). In an IdP if Sync Mode = force, it means that first name,last name and email are updated with values from IdP ( unless IdP value is null).
2. Moreover, as I see Social User Attribute mappers extend AbstractJsonUserAttributeMapper. In this class only User Attribute can be changed. In UserAttributeMapper for OIDC and SAML email, first name and last name can be changed. I believe that we should make a PR for adding them in Social User Attribute mappers.
3. Attribute value has 255 length. Maybe there is a need to change it. clob is not best solution for all User Attribute value. However, having another User Attribute object/field, means changing in Idp and Client mapper. For sure we need changes for ORCID publications. Question in dev mail list : https://groups.google.com/g/keycloak-dev/c/z6htKyfByd0. They have closed jira issue https://issues.redhat.com/browse/KEYCLOAK-9515 for this.

[cgeorgilakis]

In an IdP if Sync Mode = force, it means that first name,last name and email are updated with values from IdP ( unless IdP value is null).