empinator
opened 1 year ago
-
'@' should not be included in user login name. It should be a bug that OneDev includes that when authenticate via Azure SSO.
-
Name Previous Value Current Value Type
Improvement
Bug
Affected Versions
empty <=11.0.67
-
Name Previous Value Current Value Affected Versions
<=11.0.67
<=11.0.6
-
OneDev
changed state to 'Closed' 1 year ago
Previous Value Current Value Open
Closed
-
State changed as code fixing the issue is committed (9672ba0c)
-
OneDev
changed state to 'Released' 1 year ago
Previous Value Current Value Closed
Released
-
State changed as build OD-5403 is successful
-
Thanks for taking care of things so quickly again!
Since you mentioned that this was a bug regarding users login name, I was wondering if I have to do some sort of user migration now that this is no longer the case? Or is there anything else I have to take care of when applying this update?
-
New users will be using name without domain suffix. For existing users, you will need to change user name manually to remove the domain part.
-
thank you
| Type |
Bug
|
| Priority |
Normal
|
| Assignee | |
| Affected Versions |
<=11.0.6
|
| Labels |
No labels
|
Issue Votes (0)
Watchers (2)
Hi Robin,
we are using Azure SSO for authentification which automatically results in all usernames beeing created with the related e-mail address. Everything works smoothly, except if we are trying to reference a user in a comment by using a leading @ sign. It's possible to select the user from the appearing drop-down an add it to your comment. However, I can see that the @ itself is not included in the link and also when clicking on the username, it will lead to an e-mail being drafted to that address.
Am I correctly assuming, that if the reference would work correctly, the named user would get an issue notification e-mail?
Thanks, e.