nextcloud / nextcloud/suspicious_login
Allow list for IPs
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 106
- Forks
- 32
- Avg merge
- 8h 33m
- Merged PRs (30d)
- 10
Description
Hello,
I use your app in my nextcloud, called (a)
This one is connected to another one, called (b)
It works well and it is very interesting except :
Suspicious_login of (b) is considering webdav call of (a) as suspiscious.
I try
php occ suspiciouslogin:train
php occ suspiciouslogin:etl
php occ suspiciouslogin:optimize
Nothing changed
I would propose to add a whitelist in the code in order to whitelist some IPs
What do you think ?
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 reviewing the suspicious_login:train, suspicious_login:etl, and suspicious_login:optimize commands mentioned in the issue and reproduce the WebDAV false positive between the two Nextcloud instances. Determine where an IP allow list would fit and document the expected behavior: configured trusted IPs should no longer be treated as suspicious login sources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100