Open fetimo opened 1 year ago
I'm not aware that |
is a valid character for user ids:
https://github.com/nextcloud/server/blob/346344c15371597ec825059abdf7564da9334b7e/lib/private/User/Manager.php#L710-L715
So it also is not matched by the regular expression later on that tries to match mentions:
Interesting, thanks for the quick reply Nick! I'm not familiar with this code but I guess that SAML users don't have the same restrictions? What do you suggest in this scenario?
The auth0/saml user backend could change them before creating the users in Nextcloud. Or someone sends a PR to all place
Moving to server therefore
Which NC version?
Also happens on master. The problem is the auth0 user backend contains |
which is not matched by the regex when finding mentions in comments and anything else because the user default user backends don't support the character and it's not listed as supported in the manager.
The question is whether we want to extend the character list and allow it, or not, in which vase the auth0 backend should try to change it's account pattern and migrate existing users over
How to use GitHub
Hi, apologies if this is a duplicate issue, I have looked but couldn't see anything that looked similar.
Steps to reproduce
Expected behaviour
The message preview for a user what is sent should be consistent. E.g. when I @[person] I expect the message to show the same, rather than be replaced by their user ID.
Preview
Sent
Actual behaviour
The message is not consistent with the preview.
Talk app
Talk app version: 15.0.6
Custom Signaling server configured: yes
Custom TURN server configured: yes
Custom STUN server configured: yes
Browser
Microphone available: yes
Camera available: yes
Operating system: macOS
Browser name: Chrome
Browser version: 114
Nextcloud Version: 25.0.7 Enterprise