Validate WS Proxy functionality in CAM-Gateway
Open
Nobody has claimed this yet.
sustainment
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 2
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 2
Description
In removing the nginx gateway, some updates were needed to the demo authentication mode to ensure the WS API proxy worked. No matching original changes were identified on the cam-gateway configuration. It is unclear if that is because such updates are not needed, or if this functionality may have previously been broken in this mode.
Additional testing/validation is recommended.
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 demo authentication mode and the cam-gateway configuration, then exercise the WS API proxy in that mode. Done means determining whether proxy updates are required and documenting or addressing any functionality failure found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- networking, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100