V14: The option usernameIsEmail
is not supported
#2105
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This fixes a few things seeing that before, the option
usernameIsEmail
was not supported -- at least not set tofalse
.This adds a "username" field to the user profile settings as well as a repository/store combo to fetch the user configuration settings, which have now been added to the backend (new API models are included).
Fixes umbraco/Umbraco-CMS#16512
Types of changes
Motivation and context
Ideally, we'd like to have some kind of model state on the user details model, but for now, we can get the information through the user configuration endpoint. The only scenario we cannot solve in the UI at the moment is a more complex one where a login provider is set to "deny local login". In that case, the server will refuse any username changes.
How to test?
email
anduserName
properties).Umbraco:CMS:Security:usernameIsEmail
tofalse
Screenshots (if appropriate)