HTTP reverse-proxy service for "federated" authentification #2

New issue

Open

opened 2017-06-13 10:32:15 +00:00 by david · 1 comment

david commented

2017-06-13 10:32:15 +00:00

(Migrated from dev.cryptec.at)

A HTTP service capable of being peered to other of its kin has to be developed. It forwards authenticated and authorized requests to a ffserver instance. Alternatively it may forward it to an ngnix instance that in turn forwards it to an ffserver. The nginx will hopefully do all the legwork around streaming the result.
Authenticated and authorized requests also have to be forwarded to an Elasticsearch instance.

A HTTP service capable of being peered to other of its kin has to be developed. It forwards authenticated and authorized requests to a ffserver instance. Alternatively it may forward it to an ngnix instance that in turn forwards it to an ffserver. The nginx will hopefully do all the legwork around streaming the result. Authenticated and authorized requests also have to be forwarded to an Elasticsearch instance.

david commented

2017-06-13 10:36:08 +00:00

(Migrated from dev.cryptec.at)