OIDC Connection: Missing profile email in /api/oauth/userinfo endpoint

Found a bug? Please fill out the sections below. 👍

Issue Summary

We attempted to connect to the OIDC provider (Entra in our case). The response from api/oauth/userinfo does not provide the email attribute. After some debugging, we found that the email is parsed from the Entra user's Contact information attribute, but only if it is present. We are unsure if this is the expected behavior. The email in the contact information in Entra is not filled out by default, and there is also the possibility to add multiple emails.

Steps to Reproduce

1. Create connection in jackson dashboard
2. Select OIDC and provide all necessary fields to entra OIDC
3. try to use API

Expected behaviour could be, that email should be parsed properly from user in that case. Because entra user is having email and not need to be provided in entra users contact information.

Start by tracing the /api/oauth/userinfo endpoint and its OIDC profile mapping, focusing on how Entra user email data is selected. Compare the available Entra email attributes and verify the expected response for users without Contact information; done means the endpoint returns the appropriate email consistently and the behavior is covered by tests.