STS: Hyperlinks to Restricted Sites Remain Visible on SharePoint Team Services Web Site (317573)



The information in this article applies to:

  • SharePoint Team Services from Microsoft
  • Microsoft FrontPage 2002

This article was previously published under Q317573

SYMPTOMS

If you add a new hyperlink to a publicly available link list on a SharePoint Team Services Web site, and the resource that this new hyperlink points to is confidential (for example, it has highly restricted user permissions), the hyperlink still remains visible in the link list.

CAUSE

This behavior occurs because when you add a hyperlink to a Web page, this process does not permit you to consider NTFS resource information.

To create a dependency between a hyperlink's visibility and the link target permissions, you have to use FrontPage Web permission features.

RESOLUTION

To resolve this issue, create two different link lists. One of these lists will contain links that are intended to be viewable by all team members; this list can remain on the root Web. Store the other link list (which will contain the links to the restricted Web sites) in a separate subweb with the appropriate subweb permissions.

For example, if you have a confidential resource at the following location

http://otherserver/confidential.doc

and your publicly available link list is at the following location

http://teamserver

use FrontPage 2002 to create a Team Services subweb with separate permissions (for example, http://teamserver/secureinfo). On this subweb, you can create the second link list with a hyperlink that points to http://otherserver/confidential.doc.

Additionally, make sure that when you use Windows Explorer, the physical directory on Microsoft Internet Information Server (IIS) [for example, C:\InetPub\wwwroot\secureinfo] is not marked for indexing by Microsoft Index Server.

Modification Type:MinorLast Reviewed:1/6/2006
Keywords:kbprb KB317573