On Wed, Aug 28, 2013 at 08:18:36PM +0200, Christian Felsing wrote:
Hi there,
> Thank you for your hint, which solved this problem with a little bit LUA
> code. If LUA code (security) tests are finsihed I will publish this code.
Good to know that you found a solution.
I guess that the outline sh
Thank you for your hint, which solved this problem with a little bit LUA
code. If LUA code (security) tests are finsihed I will publish this code.
cheers
Christian
Am 27.08.2013 00:08, schrieb Francis Daly:
> The correct value is "Basic " followed by the base64-encoding of
> user:pass, where "use
On Sun, Aug 25, 2013 at 08:53:57AM +0200, Christian Felsing wrote:
Hi there,
> Nginx should be used as a reverse proxy and configured for client
> certificate authentication. Backoffice application supports basic auth only.
> Apache 2.4 solution for that kind of problems is "Fake
Sorry, does not what I need:
proxy_pass http://myapache:8000;
rewrite_by_lua '
ngx.var.remote_user = "user"
ngx.var.remote_password = "secret"
';
This should fake a 401 login but I get
2013/08/26 20:11:11 [error] 19175#0: *2 lua entry thre
verse proxy and configured for client
> certificate authentication. Backoffice application supports basic auth
> only.
> Apache 2.4 solution for that kind of problems is "Fake Basic Auth" so
> backoffice application gets a remote_user and password generated from
> client ce
Hello,
I am new to nginx and have following problem:
Nginx should be used as a reverse proxy and configured for client
certificate authentication. Backoffice application supports basic auth only.
Apache 2.4 solution for that kind of problems is "Fake Basic Auth" so
backoffice applicat
