nextcloud / nextcloud/user_saml
Disabled password modification when SAML is the only user backend
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 104
- Forks
- 85
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 16
Description
Steps to reproduce
- Configure SAML SSO
- Disable « Allow the use of multiple user back-ends (e.g. LDAP) »
- go to personnal/Security (
/index.php/settings/user/security) with an account which has an initialized password on Nextcloud
Expected behaviour
- We should not have the ability to change our password
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
Reproduce the configuration with SAML SSO as the only user backend, then open /index.php/settings/user/security with an account that has an initialized Nextcloud password. Trace how the security page handles password modification in this configuration; done means the account cannot change its password when multiple user back-ends are disabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100