Actions
Bug #3766
closed
It is impossible to know who has created or removed an API account for Rudder
Status:
Released
Priority:
1 (highest)
Assignee:
Jonathan CLARKE
Category:
Web - Maintenance
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
An API account is like an admin one since it has many rights on the application but there is no log about its creation or removal in the event log.
In this situation, it could be possible to create an API account to destroy all the configuration or do something harmful, remove the API account without knowing who where behind. In my opinion, we should at least know who created and removed any API account.
Updated by Nicolas PERRON over 11 years ago
- Tracker changed from Bug to User story
Updated by Nicolas PERRON over 11 years ago
- Target version changed from 2.7.0~beta1 to 2.7.0~rc1
Updated by
Updated by Jonathan CLARKE over 11 years ago
- Tracker changed from User story to Bug
- Status changed from New to 8
- Assignee set to Nicolas CHARLES
I absolutely agree, this is really a problem. And this is a bug, not a user story - no changes should be possible in Rudder without event logs.
Updated by Jonathan CLARKE over 11 years ago
- Priority changed from N/A to 1 (highest)
Updated by Nicolas CHARLES over 11 years ago
- Status changed from In progress to 8
Updated by Nicolas CHARLES over 11 years ago
- Status changed from 8 to In progress
Updated by Nicolas CHARLES over 11 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Jonathan CLARKE
- % Done changed from 0 to 100
- Pull Request set to https://github.com/Normation/rudder/pull/282
Updated by Nicolas CHARLES over 11 years ago
- Pull Request changed from https://github.com/Normation/rudder/pull/282 to https://github.com/Normation/rudder/pull/283
Updated by Nicolas CHARLES over 11 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset 5e46ef6e15d2888ec4010ea4b36f75632eadf68e.
Updated by Jonathan CLARKE over 11 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.7.0~rc1, which was released today.
Check out:- The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2013-July/000038.html
- The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog27
- Download information: http://www.rudder-project.org/foswiki/Download/
Actions