On Tuesday 09 April 2002 19:27, Rob Mayoff wrote:
>
> If you load ns_perm, then it will also attempt to authorize requests.
> The simplest solution is to not load ns_perm. If you do load ns_perm,
> then (I think) you may simply tell it to allow user "" to access any
> URLs that are otherwise protected by your Digest filter. Here's how.
>
> Make sure this line is in nsperm's passwd file:
>
> ""::::::
>
> (It is already in the default passwd file.) Then put this line in the
> perms file:
>
> allowuser inherit GET /my/digest-protected/url ""
>
> Substitute the appropriate URL in place of "/my/digest-protected/url".
> Repeat with different URLs as required.
If I'm not mistaken (correct me if I'm wrong, please),
but, if I do not load the ns_perm module then:
- I do not get the "allowuser" functionality (or is it "ns_perm allowuser"?)
- I lose all other user's hostname (ip/domain) checking
- Ns_AuthorizeRequest always grants access if I do not register
my own authorization callback function
If above holds true, then this can be used as a starting point
when developing DAV, indeed.
But, I'm afraid that people would really need both (basic and digest
and/or some other scheme in the future) at the same time when it comes
to deployment. That's why a hook in the Ns_AuthorizeRequest allowing
other schemes would be a good thing. Hopefully this thread will serve
as a kick for somebody to consider doing a proper integration work in
the core server.
Zoran
