openvinotoolkit / openvinotoolkit/model_server
Enabling HTTPS end points on OpenVINO Model server
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 931
- Forks
- 277
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 68
Description
Would be great if OVMS can support HTTPS end point by being to authenticate the server, as well as establish secure SSL (encrypted) channels to OVMS. I know that you an optional NGINX front end, but the problem is that communication between the NGINX and the OVMS backend is over HTTP, and thus unencrypted. We would like to up an "Inferencing Service" based on OVMS. where one of the requirements is being able to "maintain confidentiality of inferencing inputs". We use Gramine Shielded Containers to transform the standard OVMS docker image to one that can readily run within Intel SGX, and this preserve input confidentiality during execution. However, the service still cannot guarantee full confidentiality unless the endpoints are also secure. NGINX does not solve the problem. I am happy to discuss further if someone wants more information. Thanks!
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
The issue names no files or tests; begin by tracing OVMS endpoint configuration and the existing NGINX-to-OVMS arrangement. Clarify the supported authentication and TLS boundaries, then verify that the requested endpoint behavior provides encrypted communication for the stated inferencing service.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, docker, nginx
- Domain
- api, backend-api-design, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100