Actions
User story #3888
openChange account information stored in eventlog to handle API or webapp cases
Status:
New
Priority:
N/A
Assignee:
-
Category:
Web - Maintenance
Target version:
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:
Description
We need to be able to know who does what with the API. But API account can be temporary, they come and leave, with name changed, as well as token. Only their ID is permanent.
To be able to keep a track of what happen, in http://www.rudder-project.org/redmine/issues/3784 we resolved to the workaround of storing in the principal that it is an API account, with the name within (we were really in kind of a rush)
The idea of having a naming convention was that it was easier to track afterward those who should be corrected.
It would be great to have two new columns, one to say what type of account it is (REST, Webapp), and one for the ID
Actions