Tuesday, July 25, 2006

Part 2 - Enabling Anonymous Access

Earlier, I wrote a about how to implement forms authentication for a SharePoint 2007 Beta2 site. Typically, you would probably not want to apply authentication to the entire web site. You may want, for example, to allow anonymous users to view the home page.

Here's how to turn on anonymous access:

1.Enable anonymous access on the top-level web site:
a. Select Start > SharePoint 3.0 Central Administration
b. Click Application Management
c. In the "Application Security" section, click Authentication Providers.
d. Select the web application to work on.
e. Click ASpNetSqlMembershipProvider
f. Check the Enable Anonymous Access checkbox.
g. Click Save

2. Enable anonymous access at the site level
a. Navigate to the web site. You will be prompted for a user id and password. Login as the adminstrator.
b. Goto Site Actions> Site Settings > Modify All Site Settings
c. In the Users and Permissions column, choose Advanced Permissions.
d. From the menu, choose Settings > Anonymous Access




e. You could choose to allow guest users to view only lists or the entire web site. Choose to enable anonymous access on the entire web site.



3. Delete the authentication cookie
a. Select Tools > Internet Options
b. Click Delete Cookies

And the next time you open your page, you won't have to login to view the front page. To prevent anonymous users from viewing sub sites, repeat step 2 for each sub site but choose "Nothing" instead.

7 Comments:

At 3:19 AM, Anonymous sri said...

Hi,

Very useful article.

I do have a question: When some parts of a site has to authenticated when other parts are accessible anonymously, how would one go about this? I am thinking for example, some links on a web page need to force forms based authentication if not yet authenticated. Would this mean we structure the site hierarchy in such a way that anonymous pages are from a set of sites and authenticated pages are from another set of sites?

Could you also explain how authorization is done in MOSS as compared to MCMS. We currently use CMS groups and ACL channels for different CMS groups. Thanks

 
At 5:02 PM, Anonymous Nat said...

Great post - has got my anonymous auth working great. the problem for me now is that my site requires folders and pages to be locked down, any pointers on how to do this?

I've tried using >location< tags in the web.config for the portal site, but it doesn't seem to register...

Thanks!

 
At 1:51 AM, Blogger Spencer said...

Thank you.

 
At 12:49 AM, Anonymous Yehiel said...

If I have Publishing web under Publishing site, anonymous works great for father (site) and still brings auth dialog for son (web). For other templates, like Tem, it works without issues

 
At 1:06 AM, Anonymous Yehiel said...

If I have Publishing web under Publishing site, anonymous works great for father (site) and still brings auth dialog for son (web). For other templates, like Team, it works without issues

 
At 7:39 PM, Blogger Girish said...

VERY USEFUL ARTICLE>... You are simply great. Keep up the good work...

 
At 4:57 PM, Anonymous cindy said...

Good article. But I have question, how to configure or set the sub-site to be accessed by external user. E.g, I have created siteA and there are 3 sub-site: sub-SiteA, sub-SiteB and sub-SiteC. Then, only sub-SiteB can be access by external user with login screen. Any idea? Thanks


Regards
Cindy

 

Post a Comment

<< Home