I'm dealing with an OIDC situation where the access token response contains more useful properties that I need than get exposed by the User object. EPIC OAUTH implementation. For example their token response includes a patient property that would be very useful if it could be stored in the User object. UserManagerSettings seems to allow for a lot of overrides, but not which properties should be retained from the SigninResponse for the User object.

I know that they exist in the SigninResponse object, but the constructor of the user object filters that to the known properties. I like working with the events that come off the UserManager, it makes working your library easy. If I'm missing something please tell me, but I feel like we should have a setting to extend the User object.

I would be happy to work on that if interested.