Actions
Bug #15823
openName collision between api token / user token and missing error message
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
Description
If an user has the same name as an existing API token (for example, "test"), then the user can't get its API token in the "login" menu. Moreover, we only get "error 500" in that menu without really knowing what the error is.
Actions