Skip to content
This repository has been archived by the owner on May 15, 2024. It is now read-only.

Authentication of the DeStor REST API #223

Open
xinaxu opened this issue Nov 13, 2023 · 2 comments
Open

Authentication of the DeStor REST API #223

xinaxu opened this issue Nov 13, 2023 · 2 comments
Labels

Comments

@xinaxu
Copy link
Collaborator

xinaxu commented Nov 13, 2023

Authentication of the DeStor REST API itself came up. This can be done using off the shelf HTTP reverse proxy. We need docs, guidelines and maybe a demo set up on this. Seems like a low hanging fruit

We need to talk to ianconsolata on slack for use cases

@xinaxu xinaxu added the triage label Nov 13, 2023
@gammazero
Copy link
Collaborator

So, just get a certificate and terminate TLS with nginx?

@masih
Copy link
Member

masih commented Nov 16, 2023

This is than TLS termination. Here is a user story:
"As an ISV I want to be able to control who can call the Motion REST API".

This does not require much implementation; it should be achievable using the existing HTTP control plane, e.g. basic auth, JWT auth, etc.

What's asked here is an example, or documentation on how one would go about doing this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants