Project

General

Profile

Actions

Bug #10259

closed

Log for failed login attempt is not (correctly) reported

Added by François ARMAND over 7 years ago. Updated over 5 years ago.

Status:
Released
Priority:
1 (highest)
Category:
System integration
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

We don't have a WARN, synthetic log line when a people tried to log in and failed.

Proposed format:

//form login
[2017-02-22 23:18:15] WARN  application - Login authentication failed for user 'admin' from IP '0:0:0:0:0:0:0:1': Bad credentials

//rest
[2017-02-22 23:20:41] WARN  application - REST authentication failed from IP '0:0:0:0:0:0:0:1|Proxy-Client-IP:yeah-anything-can-go-here': No registered token 'xxxxx'
Actions #1

Updated by François ARMAND over 7 years ago

  • Status changed from New to In progress
Actions #2

Updated by François ARMAND over 7 years ago

  • Description updated (diff)
Actions #3

Updated by François ARMAND over 7 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/1528
Actions #4

Updated by François ARMAND over 7 years ago

  • Status changed from Pending technical review to Pending release
Actions #5

Updated by François ARMAND over 7 years ago

  • Private changed from No to Yes

Make it private, as requested by users.

Actions #6

Updated by Vincent MEMBRÉ over 7 years ago

  • Status changed from Pending release to Released
  • Priority set to 0

This bug has been fixed in Rudder 3.1.19, 4.0.4 and 4.1.1 which were released today.

Actions #7

Updated by Vincent MEMBRÉ over 5 years ago

  • Private changed from Yes to No
Actions

Also available in: Atom PDF