Matthew Gillen wrote: > Mike wrote: >> Matthew Gillen wrote: >>> site up for my project, that's it. I leverage my department's sys-admins by >>> using (via mod_pam) the user-database that they have to maintain anyway (on >>> their own budget). etc, etc. >>> >> Do you have a recipe or a link on how to set up mod_pam with Apache 2.2 >> by any chance? > > For me, it was as simple as > yum install mod_auth_pam > > and then adding the following apache config: > <LocationMatch "/tracsrv/(project1|project2).*"> > AuthType Basic > AuthName "(note to users about what username to use)" > AuthPAM_Enabled on > Require valid-user > </LocationMatch> > > Alternatively, you can replace the "Require" line with this one: > Require group XXX > if you want not only a valid user but also to ensure that use is a member of > group XXX.
Oh, and keep in mind that mod_auth_pam doesn't deal well with shadow passwords: http://pam.sourceforge.net/mod_auth_pam/faq.html (last question) I'm using NIS for my user database, so this wasn't a problem for me until I wanted to add some local users that weren't in NIS. Then I tripped over this shadow issue. But the FAQ tells you how to work around it. Matt --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
