Re: Content Sources based on Audience

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



If you index file shares and the NTFS permissions do not have read access
for the user then they should not be returned in the search results. Forget
the shared folder permissions check what your ntfs ones are and if that user
belongs to any group that has read access to that folder or file at NTFS
level then it will show up in the results , it they do have read access then
should not prompted for logon as they should be authenticated by Windows
authentication as normal through the file system. They would get asked to
authenticate if they do not have access to the shared folder though.

In answer to your second part about displaying certain Search scopes then I
believe a developer could answer this better but I would imagine it would be
possible to code what search scopes are shown on an area page based on your
Sid. I will let the Dev people expand on that one more if it is possible.

--
Steve Smith

UK Sharepoint Training
http://www.combined-knowledge.com/sharepoint_knowledge_tracks.htm


"Michael Brown" <mbrown@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1133892927.149748.153430@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Thanks for the reply Steve, the problem is that these files will return
> in the search list and when clicked upon, the users will get prompted
> for security. Ideally, if the users does not have permission or are
> not in a specific audience, then the documents would not come back in
> the search results. No reason to show users documents to which the do
> not have access.
>
> So I really would like default source contents based on audience or NT
> Groups. I imagine I could customize the system to support this, but
> was hoping there was a way to do this by default.
>
> It does not seem like this is possible without forcing the users to
> choose a content source manually.
>


.



Relevant Pages

  • Re: IIS 5 looses authenticated user
    ... > We are using NTFS Permissions. ... >> then authentication if any, then web permission, and finally ntfs ... >> localsystem for inetinfo, iwam for dllhost, and request identity is the ...
    (microsoft.public.inetserver.iis.security)
  • Re: Limit some users?
    ... authentication (they do not like running arbitrary binaries on their servers ... I suggest you only allow IIS to serve content from a NTFS partition. ... One way to do this would be to apply NTFS permissions on the web content. ...
    (microsoft.public.inetserver.iis.security)
  • Re: IIS 5 looses authenticated user
    ... We are using NTFS Permissions. ... > are you using IIS authentication? ... > then authentication if any, then web permission, and finally ntfs ...
    (microsoft.public.inetserver.iis.security)
  • Re: Item details in filestore / fileshare search results
    ... In order to ensure that people cannot see files from a file server in a ... search results they must not have NTFS permissions to that file. ... It is this NTFS security that needs to be addressed by your file system ... on the NTFS permissions of the files not the shared folder permissions. ...
    (microsoft.public.sharepoint.portalserver)
  • Re: Item details in filestore / fileshare search results
    ... Many Thanks Steve, ... search results they must not have NTFS permissions to that file. ... on the NTFS permissions of the files not the shared folder permissions. ...
    (microsoft.public.sharepoint.portalserver)