opengeospatial / opengeospatial/ogcapi-processes
How protect an individual process hosted with OGC API Processes?
Open
@jerstlouis is already working on this.
Since Dec 23, 2024.
Part 1 (Core)
Part 2 (DRU)
Part 3 (Workflows/Chaining)
Part 4 (Job Management)
- Dominant language
- AsciiDoc
- Stars
- 63
- Forks
- 46
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
Overview
An individual process hosted in a deployment of OGC API Processes shall be protected with an OpenAPI scheme, so for example API-Key. The client must send the HTTP header X-API-Key that is to be processed by the individual process.
Note
It is not the requirement to protect the entire OGC API Processes deployment.
Question
How would I describe the requirement of an API-Key header in the Process description? At the moment, there seem to be no option to describe the requirement for a particular HTTP header like X-API-Key according to the current Standard.
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.
Assessment
This issue has not been assessed yet.