Actions
Bug #27090
closed
Bad logger used for authentication error
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Very Small
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No
Description
When we have an authentication error, we have the following log
2025-06-13 08:45:49+0000 INFO application.authentication - Rudder authentication attempt for principal 'admin' with backend 'file': failure: Bad credentials 2025-06-13 08:45:49+0000 WARN application - Login authentication failed for user 'admin' from IP '127.0.0.1|X-Forwarded-For:192.168.254.62': Bad credentials
the second one ought to be application.authentication
Files
Updated by Clark ANDRIANASOLO about 2 months ago
- Related to Enhancement #25478: Normalize authentication logs added
Updated by François ARMAND about 1 month ago
- Assignee set to François ARMAND
- Priority changed from To review to 1 (highest)
Updated by François ARMAND about 1 month ago
- Status changed from New to In progress
Updated by François ARMAND about 1 month ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Clark ANDRIANASOLO
- Pull Request set to https://github.com/Normation/rudder/pull/6468
Updated by Anonymous about 1 month ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|d4899775513e6739fe734a9ab42c731e8171a8f4.
Updated by François ARMAND 29 days ago
- File clipboard-202507040932-kvn2b.png clipboard-202507040932-kvn2b.png added
- Fix check changed from To do to Checked
We now have a double log, not sure it's usefull. But at least it's in the correct logger. 
Updated by Félix DALLIDET 15 days ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.2.8 and 8.3.3 which were released today.
Actions