feat: Allow user backends to manage property permissions #58002
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
come-nc
requested review from
ArtificialOwl,
icewind1991,
leftybournes and
salmart-dev
and removed request for
a team
Not yet reflected in the UI apart from displayname/email/avatar Signed-off-by: Côme Chilliet <[email protected]>
Signed-off-by: Côme Chilliet <[email protected]>
…ions This will prevent users from editing profile fields if those are configured to be sync from LDAP. I did not include the avatar in this because it has a special handling. Signed-off-by: Côme Chilliet <[email protected]>
come-nc
force-pushed
the
fix/let-user-backend-lock-fields
branch
from
c3e27ba to
af760d1
Compare
Signed-off-by: Côme Chilliet <[email protected]>
come-nc
added
3. to review
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This allows user backends to control which account property can be edited by the users.
The existing API for display name and API are falling back on the new clean API.
Not yet reflected in the UI apart from displayname/email/avatar.
Checklist
3. to review, feature component)stable32)