This is because the subject is being pulled from the member's VMI SocialAuth id_token, which hasn't yet been created / updated since the member was created.
How to handle this will be addressed by the local member profile editing interface: It will call the VMI API, store values, receive response data, and then will need to store that locally for use in this session — the changes in VMI will not come down via the id_token until the member logs in again, so we have to store the data locally for now. We will either edit the VMI id_token, or go back to having a local copy of all of the relevant files in the UserProfile.
To reproduce:
This is because the subject is being pulled from the member's VMI SocialAuth id_token, which hasn't yet been created / updated since the member was created.
How to handle this will be addressed by the local member profile editing interface: It will call the VMI API, store values, receive response data, and then will need to store that locally for use in this session — the changes in VMI will not come down via the id_token until the member logs in again, so we have to store the data locally for now. We will either edit the VMI id_token, or go back to having a local copy of all of the relevant files in the UserProfile.