projectdiscovery / projectdiscovery/docs
Updating the blog post on dynamic auth
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 28
- Forks
- 62
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 3
Description
Hey! I'm not sure this is the right place to ask this, but could you update the Scanning Login-Protected Targets with Nuclei v3.2 blog post and fix the template in the dynamic section? The blog post ranks higher in google than the docs, so a lot of people might get stuck because the examples in the blog post don't work.
The template in the blog post:
There are two issues:
- The template still includes variables with
name:instead ofkey:which was fixed in this repo 5 months ago. - The template in the blog doesn't include the
input:property. Without it I get the following error:
[FTL] Could not fetch dynamic secret: no extracted values found for dynamic secret
It's marked as optional in the docs here, but I have hardcoded urls in my login template, but I'm still getting the error.
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
Read tools/nuclei/authenticated-scans.mdx around the linked section and compare it with the linked blog post’s dynamic-auth example. Confirm the blog example matches the documented key and input behavior, then verify that the reported dynamic-secret error is no longer produced.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100