-
Notifications
You must be signed in to change notification settings - Fork 227
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
how to secure operating api #680
Comments
Unfortunately, there is no concept of |
good to know. to have access control to /v1/apps (deploying and updating apps), what kind of middleware will i need to write? is there a guide somewhere? |
You don't need to write any middleware. You just need to pass an ENV when starting the functions server. You also need to pass the same token when you are issuing commands via the If you need to modify the implementation (write your own middleware etc), please check the following PRs, they may give you ideas. Thank you ! |
hmm i can't find the name of the env...help pls? for my use case, i would really need a per-user jwt token as described before. Is this already on your roadmap? I would certainly like to help on this feature if you think it's a good idea. |
does this help ? As for users, I am afraid that is not in the roadmap. If you are willing to help though, of course we would appreciate your input ! |
tks that certainly helps. I'll try to implement users then... |
its my first time trying this project. i must be missing something in the docs, but how to i secure app creation api? like, is there a concept of users here? set the number of apps a user can create? give a user some kind of api key to protect his app routes from unauthorized editing? do i need to rite jwt middleware for all that?
The text was updated successfully, but these errors were encountered: