Vcenter is protected, facing 403 client error
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 1
- Forks
- 2
- Avg merge
- 1h 37m
- Merged PRs (30d)
- 5
Description
Describe the bug
Hi how do I add basic auth when I generate the api spec? My vcenter api host is basic auth protected
Reproduction steps
- Run steps in guide
...
Expected behavior
Got 403 forbidden error
Additional context
No response
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 following the guide referenced in the reproduction steps and reproduce the 403 response against the protected vCenter API host. Trace the API-spec generation entry point and its authentication configuration. Done means the documented generation flow handles the host's basic authentication without returning 403.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100