ORCID Identity Providers Mappers Problems

[cgeorgilakis]

• We have problem for large user attributes like publications. See bullet three of related issue 128
• Current Keycloak implementation for User info parsing can not support ORCID verified attribute even if they accept our PR 8018. person.emails.email consists list of emails. If I find attribute primary in any element of the list, I put this email as User email. We need to check if this email has attribute verified equals to true. With current Keycloak Social User Attribute parsing we can only check attribute verified of first email in the list.
  I propose to add a specific field 'email verified check' or mapper for check emailVeriifed without any other configuration. Field solution is better if it is possible to be implemented in the extension.

[cgeorgilakis]

Issue close. The only problem that we will have generic fix is the first bullet