Project

General

Profile

Actions

Bug #28860

closed

Wrong Error Message/Return code getting after exceeding the 'failed_login_attempts_limit'

Added by Tomer Brisker over 4 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Category:
Authentication
Target version:
-
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1778599

Description of problem:
Wrong Error Message/Return code(Internal server error) getting after exceeding the 'failed_login_attempts_limit'

Version-Release number of selected component (if applicable):

How reproducible:
Always

Steps to Reproduce:
[root@satellite]# hammer -u admin -p changeme settings set --name failed_login_attempts_limit --value 5

Setting [failed_login_attempts_limit] updated to [5].
[root@satellite ~]# for i in 1 2 3 4 5; do hammer -u admin -p WRONG_PASS user list; done
Unable to authenticate user admin
Unable to authenticate user admin
Unable to authenticate user admin
Unable to authenticate user admin
Unable to authenticate user admin

[root@satellite ~]# hammer -u admin -p changeme user list
undefined local variable or method `logger' for #<Foreman::BruteforceProtection:0x00007f80b6979698>

Actual results:
Error Message is shown as 'undefined local variable or method `logger' for #<Foreman::BruteforceProtection:0x00007f80b6979698>' and error code is '70'

Expected results:
Error Message is Incorrect and Return code should be '129'


Related issues 1 (0 open1 closed)

Related to Foreman - Feature #26887: graphql login: count login failures as brute force attemptsClosedTimo GoebelActions
Actions

Also available in: Atom PDF