Fields changed

description: Description of problem:
"failedLoginAttempts" attribute gets triggered only during a offline failed
authentication and resets to zero when the authentication succeeds. There is no
threshold set for failed login attempts

Version-Release number of selected component (if applicable):
sssd-1.1.0-2.pre20100317git0ea7f19.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Configure sssd.
2. Make sure authentication works by authenticating against a LDAP server.
3. Remove the sssd client from the network.
4. Try to authenticate with wrong password.

Actual results:
"failedLoginAttempts" attribute gets updated by one for every incorrect
password and resets to 0 when correct password is entered.

Expected results:
1. Should have a offline threshold for failed login attempts.
2. Should have a offline lockout duration after which the "failedLoginAttempts"
resets to zero and the user can retry entering his correct password.
3. Should have a offline max password life time.

=> Description of problem:
"failedLoginAttempts" attribute gets triggered only during a offline failed
authentication and resets to zero when the authentication succeeds. There is no
threshold set for failed login attempts

Version-Release number of selected component (if applicable):
sssd-1.1.0-2.pre20100317git0ea7f19.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
#. Configure sssd.
#. Make sure authentication works by authenticating against a LDAP server.
#. Remove the sssd client from the network.
#. Try to authenticate with wrong password.

Actual results:
"failedLoginAttempts" attribute gets updated by one for every incorrect password and resets to 0 when correct password is entered.

Expected results:
#. Should have a offline threshold for failed login attempts.
#. Should have a offline lockout duration after which the "failedLoginAttempts"
resets to zero and the user can retry entering his correct password.
#. Should have a offline max password life time.

Fields changed

description: Description of problem:
"failedLoginAttempts" attribute gets triggered only during a offline failed
authentication and resets to zero when the authentication succeeds. There is no
threshold set for failed login attempts

Version-Release number of selected component (if applicable):
sssd-1.1.0-2.pre20100317git0ea7f19.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
#. Configure sssd.
#. Make sure authentication works by authenticating against a LDAP server.
#. Remove the sssd client from the network.
#. Try to authenticate with wrong password.

Actual results:
"failedLoginAttempts" attribute gets updated by one for every incorrect password and resets to 0 when correct password is entered.

Expected results:
#. Should have a offline threshold for failed login attempts.
#. Should have a offline lockout duration after which the "failedLoginAttempts"
resets to zero and the user can retry entering his correct password.
#. Should have a offline max password life time.

=> Description of problem:
"failedLoginAttempts" attribute gets triggered only during a offline failed
authentication and resets to zero when the authentication succeeds. There is no
threshold set for failed login attempts

Version-Release number of selected component (if applicable):
sssd-1.1.0-2.pre20100317git0ea7f19.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Configure sssd.
2. Make sure authentication works by authenticating against a LDAP server.
3. Remove the sssd client from the network.
4. Try to authenticate with wrong password.

Actual results:
"failedLoginAttempts" attribute gets updated by one for every incorrect password and resets to 0 when correct password is entered.

Expected results:
1. Should have a offline threshold for failed login attempts.
2. Should have a offline lockout duration after which the "failedLoginAttempts"
resets to zero and the user can retry entering his correct password.
3. Should have a offline max password life time.

https://bugzilla.redhat.com/show_bug.cgi?id=576623

description: Description of problem:
"failedLoginAttempts" attribute gets triggered only during a offline failed
authentication and resets to zero when the authentication succeeds. There is no
threshold set for failed login attempts

Version-Release number of selected component (if applicable):
sssd-1.1.0-2.pre20100317git0ea7f19.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Configure sssd.
2. Make sure authentication works by authenticating against a LDAP server.
3. Remove the sssd client from the network.
4. Try to authenticate with wrong password.

Actual results:
"failedLoginAttempts" attribute gets updated by one for every incorrect password and resets to 0 when correct password is entered.

Expected results:
1. Should have a offline threshold for failed login attempts.
2. Should have a offline lockout duration after which the "failedLoginAttempts"
resets to zero and the user can retry entering his correct password.
3. Should have a offline max password life time.

=> Description of problem:
"failedLoginAttempts" attribute gets triggered only during a offline failed
authentication and resets to zero when the authentication succeeds. There is no
threshold set for failed login attempts

Version-Release number of selected component (if applicable):
sssd-1.1.0-2.pre20100317git0ea7f19.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Configure sssd.
2. Make sure authentication works by authenticating against a LDAP server.
3. Remove the sssd client from the network.
4. Try to authenticate with wrong password.

Actual results:
"failedLoginAttempts" attribute gets updated by one for every incorrect password and resets to 0 when correct password is entered.

Expected results:
1. Should have a offline threshold for failed login attempts.
2. Should have a offline lockout duration after which the "failedLoginAttempts" resets to zero and the user can retry entering his correct password.
3. Should have a offline max password life time.

From the sssd.conf manpage:

       offline_credentials_expiration (integer)
           If the authentication provider is offline, how long should we allow
           cached logins (in days since the last successful online login).
           Default: 0 (No limit)
       offline_failed_login_attempts (integer)
           If the authentication provider is offline, how many failed login
           attempts are allowed.
           Default: 0 (No limit)
       offline_failed_login_delay (integer)
           The time in minutes which has to pass after
           offline_failed_login_attempts has been reached before a new login
           attempt is possible.
           If set to 0 the user cannot authenticate offline if
           offline_failed_login_attempts has been reached. Only a successful
           online authentication can enable enable offline authentication
           again.
           Default: 5

resolution: => invalid
status: new => closed

Fields changed

rhbz: => 0

Fields changed

milestone: NEEDS_TRIAGE => void

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/1477

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.