Authentication test plan
Open
Nobody has claimed this yet.
QA:team
- Dominant language
- Shell
- Stars
- 16
- Forks
- 16
- Avg merge
- 11h 11m
- Merged PRs (30d)
- 1
Description
Based on what needs to be retested for https://github.com/owncloud/core/issues/30157
- Regression testing: authenticate then webdav operation to confirm it works
- cadaver (no session)
- web browser + Webdav uploads
- desktop client
- mobile client
- same with regular password
- same with app password
- shibboleth
- oauth
- impersonate app
- test upgrading with active app password / session ?
- same as above but add a lock-out feature:
- brute-force protection with fail2ban which parses logs
- LDAP/Active Directory lock out
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 reading owncloud/core#30157 to identify the authentication changes that require retesting. Turn the listed client, credential, identity-provider, upgrade, and lock-out scenarios into an executable test plan, then verify each case across the named clients and authentication methods. Done means the relevant cases are documented with their expected results and coverage is complete.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, testing
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100