User story #3888
openChange account information stored in eventlog to handle API or webapp cases
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
Updated by François ARMAND over 11 years ago
- Subject changed from Be able to trace all modification made by an API account in the eventlog to Change account information stored in eventlog to handle API or webapp cases
- Status changed from New to 8
Updated by Nicolas PERRON about 11 years ago
- Target version changed from 2.8.0~beta1 to 2.8.0~rc1
Shouldn't we add this feature in Rudder 2.8 ? (does not seem to be easy...)
Updated by Vincent MEMBRÉ about 11 years ago
This will not be done in 2.8.0, and is postponed to a later version.
Updated by Vincent MEMBRÉ about 11 years ago
- Target version changed from 2.8.0~rc1 to Ideas (not version specific)
Updated by François ARMAND almost 7 years ago
- Assignee deleted (
François ARMAND)