NAP WAF: Missing Brute Force log variables in docs
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- nginx
- Domain
- documentation
Research direction
Open content/nap-waf/v4/logging-overview/security-log.md and content/nap-waf/v5/logging-overview/security-log.md, then review their Available Security Log Attributes sections. Add the $username and $login_result variables with their descriptions to both pages; done means the Brute Force log variables are documented consistently in v4 and v5.
Written by the indexing model from the issue text.
Description
Describe the bug
When the Brute Force feature was released in NAP WAF 4.13, some log variables essential to this feature were missed from the documentation.
In summary, the $username and $login_result variables (and their descriptions) are missing from the Available Security Log Attributes section on the v4 security log and v5 security log pages.
To reproduce
N/A
Expected behavior
A clear and concise description of what you expected to happen.
Your environment
- Version/release of this project or specific commit
- Target deployment platform
Additional context
Add any other context about the problem here.
Sensitive Information
Remember to redact any sensitive information such as authentication credentials or license keys.
- Dominant language
- HTML
- Stars
- 94
- Forks
- 174
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 66
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.
More from nginx/documentation
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
nginx/documentation#2141 ·
-
Basic auth Open
Difficulty 3/5 1-2 days Newbie friendliness 25/100
nginx/documentation#2211 · 1 comment ·
-
F5 NGINX Glossary Open
Difficulty 3/5 1-2 days Newbie friendliness 20/100
nginx/documentation#2193 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
nginx/documentation#2158 ·
-
Http://org.sbs Open
Difficulty 1/5 Under an hour Newbie friendliness 10/100
nginx/documentation#2085 ·
All issues in nginx/documentation
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100