If we want to move to using email address based usernames, we need a way to let users change their email address (and subsequently username) that are associated with the account.
Instead of adding yet another POST API for the username (you can already change the email and the password), we could introduce a single API to update user fields: https://server/pathname/version/username NOTE: Requires basic authentication with the username and password associated with the account. The auth username must match the username in the path. Changes one or several fields for the user with the values specified in a json mapping provided in the POST body. Allowed fields are: email, username, password. The server will return 'success' on success, or an error message if some portion of the process fails. (possible failures include: username already taken -- with a new 400 code at https://wiki.mozilla.org/Labs/Weave/1.0/ResponseCodes)
This should probably be part of the user API, moving to the Reg Server component now that it exists ;)
Assignee: telliott → nobody
Component: Server: Sync → Server: Registration
QA Contact: sync-server → reg-server
Sounds like this is still useful, Added in https://wiki.mozilla.org/Services/Server/NextFeatures
Severity: normal → enhancement
There already exists both of these capabilities in the API. However, that's actually a bad thing. We should be getting rid of the ability to change your username, and should only change the email address - which then becomes your username. A small minority of our users have non-munged-email usernames, but the rest are used to the idea that email is the username. we should continue to support this moving forwards.
This is now BID's problem.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.