You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For now, we are assuming that both origami-server and deploy-manager are running on the same host, so there is no need to set up authentication for this, we can simply bind the server to the loopback address and then origami-server can communicate with it internally without being exposed outside the host. But at some point of time, we will need to extend to a different server, wherein one server will have all the demos and other running origami-server, for such cases we need some sort of authentication.
The method that I have in mind is authentication via JWT, we can simply use Nginx reverse proxy to set up TLS for origami-daemon(so we don't have to set up anything for origami-daemon) and then we can simply authenticate origami-server via JWT. This way we can also provide an admin panel sort of thing for demo deployment.
The text was updated successfully, but these errors were encountered:
For now, we are assuming that both origami-server and deploy-manager are running on the same host, so there is no need to set up authentication for this, we can simply bind the server to the loopback address and then
origami-server
can communicate with it internally without being exposed outside the host. But at some point of time, we will need to extend to a different server, wherein one server will have all the demos and other running origami-server, for such cases we need some sort of authentication.The method that I have in mind is authentication via JWT, we can simply use Nginx reverse proxy to set up TLS for origami-daemon(so we don't have to set up anything for origami-daemon) and then we can simply authenticate origami-server via JWT. This way we can also provide an admin panel sort of thing for demo deployment.
The text was updated successfully, but these errors were encountered: