|
On 3/22/05, Greg Pierce said:
>>Let us know if you have any questions!
>
>I assume that in all cases the existing security preferences set
>under
>/Preferences/Web Server override these settings? Is that correct?
Those preferences are dealt with first. If they lock someone out,
the new security settings won't let you in.
However, if the security preferences let you in, the newer ones can
still exclude you.
In other words, the new security settings will never let someone in
who couldn't already access the site.
There is one special rule I haven't mentioned yet.
The difficult part, for me, was figuring out how to deal with the
discussion group messges at their own URL's. Technically, they're
served through the root folder. If you want to limit access to the
entire site then you'll want to set the security on the root
folder... but that would also prevent anyone from accessing the
discussion group messages, and there's no single page for the DG
messages where the security could be overridden to allow access.
So, the solution:
1. Set "Allow non-members to view full site" to "Yes."
2. Set the root folder's security to something like "Members Only".
3. (Perhaps set the index page, at the root of the site, to "No
Restrictions", so that guests can at least see the home page.)
The result is that your site now has a sort of "deny-then-allow"
security policy, where the default for all pages is "only members
have access." The "Allow non-members to view full site" preference
is treated as an override, saying that you want guests to be able to
view the DG.
Understand?
Seth
|
