Actions
Bug #15823
open
Name 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.
Updated by François ARMAND over 4 years ago
- Severity changed from Major - prevents use of part of Rudder | no simple workaround to Minor - inconvenience | misleading | easy workaround
- Priority changed from 41 to 22
In fact, it may be seen as a feature. And it's very easy to workaround, since the token name can be changed without any change in its usage (we don't use the name for anything else than displaying)
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 5.0-1.3 to 5.0-1.4
- Priority changed from 22 to 21
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 5.0-1.4 to 5.0-1.5
- Priority changed from 21 to 19
Updated by Vincent MEMBRÉ 9 months ago
- Target version changed from 5.0-1.5 to 7.2
- Priority changed from 19 to 0
Updated by
Actions