-
Suggestion
-
Resolution: Won't Do
-
None
-
None
-
3
-
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
It has come to our attention that certain companies have the security policy to completely lock an account completely, after a certain number of failed password attempts.
Currently, Confluence allows the user to still login with the correct password after the maximum failed attempts, as long as they enter the correct Captcha.
We need to allow admins the ability to completely lock the account after a number of failed attempts, something like what this query does:
UPDATE cwd_user_attribute c JOIN cwd_user u ON c.user_id = u.id SET c.attribute_value = 'true', c.attribute_lower_value = 'true' WHERE u.user_name = '<username>' AND c.attribute_name = 'requiresPasswordChange';
Where <username> is the user's username.
- relates to
-
CONFCLOUD-37575 Option To Lock User Out Permanently After Maximum Failed Password Attempts
- Closed
- mentioned in
-
Page Failed to load
[CONFSERVER-37575] Option To Lock User Out Permanently After Maximum Failed Password Attempts
Workflow | Original: JAC Suggestion Workflow 4 [ 3574594 ] | New: JAC Suggestion Workflow 3 [ 4335936 ] |
Workflow | Original: JAC Suggestion Workflow 2 [ 3180384 ] | New: JAC Suggestion Workflow 4 [ 3574594 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JAC Suggestion Workflow [ 3039787 ] | New: JAC Suggestion Workflow 2 [ 3180384 ] |
Resolution | New: Won't Do [ 10000 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Resolved [ 5 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2538714 ] | New: JAC Suggestion Workflow [ 3039787 ] |
Support reference count | Original: 1 | New: 3 |
Support reference count | Original: 3 | New: 1 |
Workflow | Original: Confluence Workflow - Public Facing v3 [ 2282616 ] | New: Confluence Workflow - Public Facing v4 [ 2538714 ] |
Status | Original: Needs Verification [ 10004 ] | New: Gathering Interest [ 11772 ] |
Support reference count | New: 3 |
Thank you for raising this suggestion.
We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.
For more context, check out our Community blog on our updated workflow for Suggestions
Cheers,
Confluence Product Management