nextcloud / nextcloud/password_policy
[Bug]: password-policy not working properly v33
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 39
- Forks
- 27
- Avg merge
- 1h 36m
- Merged PRs (30d)
- 10
Description
⚠️ This issue respects the following points: ⚠️
- This is a bug, not a question or a configuration/webserver/proxy issue.
- This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
- Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
- I agree to follow Nextcloud's Code of Conduct.
Bug description
Tested to set a password-policy under "Security" for the Login Policy. It is not possible with version 33 to either set "password history size" or "Maximum login attempts" or "number of days". After leaving the security page the values remain 0
Steps to reproduce
- Install or Update Nextcloud v33
- Try to set a login-policy
Expected behavior
Values which were set should remain after leaving the page
Nextcloud Server version
33
Operating system
Debian/Ubuntu
PHP engine version
None
Web server
None
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Upgraded to a MAJOR version (ex. 31 to 32)
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
- Default user-backend (database)
- LDAP/ Active Directory
- SSO - SAML
- Other
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue from the Security page on Nextcloud Server 33 after a major-version upgrade, using the login-policy settings for password history size, maximum login attempts, and number of days. Check whether each value changes before leaving the page and remains afterward. Done means the configured values persist instead of reverting to 0.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100