When changing the self-asserted first name (chosen name) , the current mobile apps still send this as given name.
We\'ve updated the backend to use givenname for the formal first name of the user. The current mobile apps do not send a chosen name field when updating the first name of the user.
Updated apps shuld only send the chosen name when the user updates the self-asserted first name, and mobile apps should not be able to overwrite the formal first name by this API call.
Expected behavior to support old and new apps:
If the app sends only a givenname to /mobile/api/sp/update (old app) update the self-asserted chosenname field
If the app sends only the chosen name (new app) update the self-asserted chosenname field.
Is the app sends both the givenname as the chosenname field, produce an error the formal-givenname can\'t be updated this way
If a current validated name is registered, the givenname and lastname fields in the update is ignored.
If no current validated name is registered, the chosenname also updated the givenname
This issue is imported from pivotal
We\'ve updated the backend to use givenname for the formal first name of the user. The current mobile apps do not send a chosen name field when updating the first name of the user.
Updated apps shuld only send the chosen name when the user updates the self-asserted first name, and mobile apps should not be able to overwrite the formal first name by this API call.
Expected behavior to support old and new apps:
If a current validated name is registered, the givenname and lastname fields in the update is ignored. If no current validated name is registered, the chosenname also updated the givenname