authentication being passed to php

[Igor Sysoev]

On Thu, Jul 23, 2009 at 11:22:19AM +0100, nginx.mailinglist wrote:

> Thank you
> I see that works fine for that particular user:pass combo
> 
> but (sorry to be a pain)
> 
> that means i have to encode the user:pass combination into the config file
> 
> what happens if there are thousands of user:pass combinations?
> 
> how can this info be dynamically passed to the php backend for
> authentication to occur there (by looking up in a database for example)?
> 
> i cant be updating the config file everytime a new user is added that can be
> crazy especially if there are thousands or more users
> 
> Regards
> 
> edit: i google and found this old email conversation on nginx mailinglist
> http://markmail.org/message/tl7h2fclizgptwnr#query:NGINX%20PHP%20AUTHENTICATION+page:1+mid:f3xw2gjllat6urff+state:results

I do not understand your problem.
nginx passes client's user:pass in Authorization header transparently.

> 2009/7/23 Igor Sysoev <is at rambler-co.ru>
> 
> > On Thu, Jul 23, 2009 at 10:50:12AM +0100, nginx.mailinglist wrote:
> >
> > > Hello
> > > just a quick question
> > >
> > > in lighttpd i was able to pass the username and pass from the url to php
> > > backend
> > >
> > > but nothing happens in nginx?
> > >
> > > let me explain
> > >
> > >
> > > lets say you have a URL like this
> > >
> > > http://userX:passY@example.com/bleh.php
> > >
> > >
> > > i expect my php backend to have user and pass entries in the $_SERVER
> > > variable as happens with lighttpd
> > >
> > > am i missing something with nginx? is it even possible?
> >
> > $echo userX:passY | perl -MMIME::Base64 -lne 'print encode_base64 $_'
> > dXNlclg6cGFzc1k=
> >
> >      proxy_pass http://example.com/bleh.php;
> >      proxy_set_header  Authorization "Basic dXNlclg6cGFzc1k=";
> >
> >
> > --
> > Igor Sysoev
> > http://sysoev.ru/en/
> >
> >

-- 
Igor Sysoev
http://sysoev.ru/en/