Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve TOTP authenticator to skip locking account when account lock is disabled #198

Conversation

sadilchamishka
Copy link
Contributor

@sadilchamishka sadilchamishka commented Jan 19, 2025

Purpose

When account locking is disabled, there is no governance connector config whether account lock on failed login is enabled or disabled (The config exists only if enabled). Due to that existing logic fails to detect the account locking is disabled.

The issue doesn't exist for a fresh setup where the account lock on failed login is not yet enabled. The issue arises after enabling and, then again disabling the account lock on failed login.

Under above mentioned state, there can be scenarios TOTP authenticator is being used as second factor with account lock happens even it was not configured by the Administrator.

The Administrator must intentionally disable account locking on failed attempts for the situation mentioned above. Correcting the buggy behavior can be done without requiring any notification.

Related Issues

@jenkins-is-staging
Copy link

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/12853283461

@jenkins-is-staging
Copy link

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/12853283461
Status: failure

@sadilchamishka sadilchamishka merged commit 6f93cab into wso2-extensions:master Jan 20, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants