Mongrel users - Mar 2007 - Fwd: Re: Basic authentication with Apache and Mongrel

There is a big difference if you are not running a pure rails site. I am doing
auth apache-side because I serve static content, perl scripts via cgi and feed
the mongrel pack from Apache.

The REMOTE_USER variable value can be passed to rails using a technique
described deep down in one of the informative pieces on the Mongrel website.

Bill

On Mon, 12 Mar 2007 17:54:07 -0700, Matte Edens wrote:

> I don''t see the difference with this and a simple static
apache site. It''s

> still Apache in front of the proxy (as the proxy) doing the auth.
I''m doing

> it.  That is if you''re not involved with a complicated
multi-server setup.

>

> Also, if you''re using Rails, you can do basic auth with the

> "simple_http_auth" plugin.  FYI.  I''ve used it.
 It''s cool.  And easier,

> IMHO, than setting up users on the server side with htpasswd, etc.  but
be

> careful if you''ve got an open SVN repository.

>

> matte

>

> Niall O Broin wrote:

>> I recently moved an app. from lighttpd + fastcgi to apache 2.2
+

>> mod_proxy_balancer + Mongrel. On lighttpd, I was using basic
authentication

>> with a configuration like this:

>>

>> auth.backend = "htpasswd"

>> auth.backend.htpasswd.userfile = "/path/to/htpasswd"

>> auth.require = ("/" => ("method"
=> "basic", "realm" => "My Realm",

>> "require" => "valid-user"))

>>

>> which was nice and simple - just as simple as using basic auth.
with a

>> static Apache site.

>>

>> Is there any way of doing such authentication with apache 2.2 +

>> mod_proxy_balancer + Mongrel ? All I''ve been able to
find with google

>> suggests that I can''t do this and I will require some
app. level

>> authentication, and I really don''t want to have to do
that.

>>

>

> _______________________________________________

> Mongrel-users mailing list

> Mongrel-users-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org

> http://rubyforge.org/mailman/listinfo/mongrel-users

>

> ** Classified by CRM114 SS as good **

> CLASSIFY fails; success probability: 0.1452  pR: -0.7699

> Best match to file #1 (nonspam.css) prob: 0.8548  pR: 0.7699 Total
features

> in input file: 3653

> #0 (spam.css): features: 1609955, hits: 159866, prob: 1.45e-01, pR:
 -0.77 #1

> (nonspam.css): features: 1618666, hits: 136684, prob: 8.55e-01, pR:  
0.77

Well, yeah.  What I meant was that the Apache-side auth process isn''t 
any different between a dynamic site and a static site.  The difference 
enters in when you need to process past apache.

Sorry for the confusion.

matte

Bill Tribley wrote:
> There is a big difference if you are not running a pure rails site. I 
> am doing auth apache-side because I serve static content, perl scripts 
> via cgi and feed the mongrel pack from Apache.
>
> The REMOTE_USER variable value can be passed to rails using a 
> technique described deep down in one of the informative pieces on the 
> Mongrel website.
>
> Bill
>
>
> On Mon, 12 Mar 2007 17:54:07 -0700, Matte Edens wrote:
> > I don''t see the difference with this and a simple static
apache site.
> It''s
> > still Apache in front of the proxy (as the proxy) doing the auth.
I''m
> doing
> > it.  That is if you''re not involved with a complicated
multi-server
> setup.
> >
> > Also, if you''re using Rails, you can do basic auth with the
> > "simple_http_auth" plugin.  FYI.  I''ve used it. 
It''s cool.  And easier,
> > IMHO, than setting up users on the server side with htpasswd, etc. 
>  but be
> > careful if you''ve got an open SVN repository.
> >
> > matte
> >
> > Niall O Broin wrote:
> >> I recently moved an app. from lighttpd + fastcgi to apache 2.2 +
> >> mod_proxy_balancer + Mongrel. On lighttpd, I was using basic 
> authentication
> >> with a configuration like this:
> >>
> >> auth.backend = "htpasswd"
> >> auth.backend.htpasswd.userfile = "/path/to/htpasswd"
> >> auth.require = ("/" => ("method" =>
"basic", "realm" => "My Realm",
> >> "require" => "valid-user"))
> >>
> >> which was nice and simple - just as simple as using basic auth.
with a
> >> static Apache site.
> >>
> >> Is there any way of doing such authentication with apache 2.2 +
> >> mod_proxy_balancer + Mongrel ? All I''ve been able to find
with google
> >> suggests that I can''t do this and I will require some
app. level
> >> authentication, and I really don''t want to have to do
that.
> >>
> >
> > _______________________________________________
> > Mongrel-users mailing list
> > Mongrel-users at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/mongrel-users 
> <http://rubyforge.org/mailman/listinfo/mongrel-users>
> >
> > ** Classified by CRM114 SS as good **
> > CLASSIFY fails; success probability: 0.1452  pR: -0.7699
> > Best match to file #1 (nonspam.css) prob: 0.8548  pR: 0.7699 Total 
> features
> > in input file: 3653
> > #0 (spam.css): features: 1609955, hits: 159866, prob: 1.45e-01, pR: 
>  -0.77 #1
> > (nonspam.css): features: 1618666, hits: 136684, prob: 8.55e-01, pR:   
> 0.77
> ------------------------------------------------------------------------
>
> _______________________________________________
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/mongrel-users/attachments/20070313/d43545d9/attachment.html