Randy wrote:

Shannon,

Thank you for getting back to me!

I am running a newer version of apache that only has
the httpd.conf configuration file.  The text that I
placed in the file is as follows:

#########################################3333 # Stuff added by Randy alias /protected "/var/www/protected/" <Directory /protected> # This is the standard authentication stuff AuthName "Foo Bar Authentication" AuthType Basic PerlAuthenHandler Apache::AuthenNIS # Standard require stuff, NIS users or
groups, and # "valid-user" all work OK require user username require valid-user # The following is actually only needed when
authorizing # against NIS groups. This is a separate
module. #PerlAuthzHandler Apache::AuthzNIS </Directory> #



As far as the .htaccess file is concerned, I only did
a "touch .htaccess" to create the file in the
/protected directory. I did not find any
documentation on WHAT needed to be put into the file. Also, should there be a .so module file for authenNIS
in my httpd.conf file?


Again, Thanks!
Randy



Hi!

Finally had a chance to take a look at your stuff, and I think this is more of an Apache config problem than anything. If you throw something like:



<Limit GET PUT DELETE PROPFIND PROPPATCH MKCOL COPY MOVE LOCK UNLOCK>
require valid-user
</Limit>
AuthName "Foo Bar Authentication"
AuthType Basic

into a .htaccess file in the directory, it will respond with the appropriate 401 header. (For some reason this same code in the <Directory> directive is not being read, (I have never aliased a directory without a .htaccess, so maybe that is it... You can probably try: http://httpd.apache.org/userslist.html. (I'm using apache1.3.27 for these tests).

BTW, Apache-AuthenNIS only queries the passwd.byname file at this time, which probably won't work in your environment, as most distros use shadow passwords at the very least now. I need to get excited about getting this working using the shadow.byname, so that we can find a real use for it nowadays... ;)

HTH,
speeves
cws



Reply via email to