Azure AD B2C mapping fails after upgrade from 4.1.1 to 4.3.0

[shineability]

Apparently the mapUserToObject method has changed and added some extra mappings in 4.3.0.

In one of our projects, the claims coming from a client's AD B2C account - to which we don't have access - don't contain a name or emails claim and thus existing code breaks.

Is the solution to update the package providing (empty) defaults for the extra mappings or would you argue that the claims SHOULD always be present in the payload?

Related issue #1165

[atymic]

Feel free to PR, or attach a sample response to this ticket so we can look.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.