-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Feature request: prevent certain changes to user profiles #5267
Comments
Related: #4708 |
I'm trying to think how this would work. You could set it on a room level, that way all servers participating would have to respect the rule. Or you could do it on a server level (which I think is what you are asking for), but I'm not sure that makes sense if the server then federates with other servers that do not enforce profile change. |
Well, a server is coupled to an identity server, which is where the accounts will come from. Putting it on the same level as the accounts itself sounds most logical? The use case here is company LDAP accounts and preventing people from impersonating each other within the company. |
That is not how accounts work. Identity servers provide identity lookup functionality only (mapping from e-mails and phone numbers to Matrix IDs) Accounts are stored and owned by their respective homeserver currently, in future they may be more fluid. |
Well, not to sound rude, but as an administrator I don't really care about that implementation detail, I just want to be able to prevent users from impersonating each other, like how many other messaging platforms such as Rocket Chat will lock usernames to whatever is in LDAP. Seeing how the homeserver knows the accounts, limiting on homeserver level seems most logical, because we can't expect matrix.org to enforce a lack of nick changes, but you still wouldn't want your employees to change their username when talking to people on matrix.org. You want certainty for the accounts that are managed by your organisation, both for communication inside it and communication with other servers you decided to link to. |
see also: #5241 |
Yeah LDAP support is not exactly matrix's strongest feat atm.. |
I believe this was fixed by #7096. |
Description:
It would be great if we could disable some user profile changes, like changing the display name, for on servers where this is set by the identity server on login.
The text was updated successfully, but these errors were encountered: