I rolled my own in Tcl. It loads a file of usernames/passwords every 15
mins. It stores these in nsv arrays. Pretty simple, and fast enough. I have
a request processor registered at preauth that checks a urlacls file that
contains each ACL'd URL and causes a challenge to be issued based on the
info in it.
Why not use nsperms? Because it didn't fit my needs and was a bit too
restrictive for me. I need to be able to check for a client SSL certificate
first, then failover to username password.
/s.
> At 10:56 AM 8/8/01, you wrote:
> >How do I get Aolserver to recognize that a user has been manually
updated in
> >the passwd file on disk without restarting/HUPing the server? I have
> >"Skiplocks" set to off in my config file (if its on and I try
ns_passwdcheck
> >it crashes the server hard without a log entry)...
> >
> >It would be really nice to be able to check this without having to build
a
> >proc to manually process the file each time a request is made and without
> >the connectivity downtime caused by a server reload...
> >
> >Thanks
>
> I think you will need to create a custom module to do this for you. There
> is no code I am aware of that reloads the files off disk. Short of
> checking on each request, you may consider:
>
> A) A scheduled proc that checks/reloads every five minutes
> B) A web interface to the passwd file that reloads the file after
updating it
> C) A web page/url that shell scripts could use to get the file reloaded
> for them:
> in other words if you have a shell script that updates the passwd
file for
> you, the shell script could do an http request on something like
> /passwd-reload
> to get a tcl script within aol server to reload the passwd file
>
>
> Jerry
> =====================================================
> Jerry Asher [EMAIL PROTECTED]
> 1678 Shattuck Avenue Suite 161 Tel: (510) 549-2980
> Berkeley, CA 94709 Fax: (877) 311-8688
>
>
>
