Skip to Content
author's profile photo Former Member
Former Member

Restrict access to Personal Directories in Filesystem Repositories

If we would index the Personal Directories of all Employees (Integrate them into an File System Repository), so that every Employee can search public documents PLUS his own personal files(trex), there are a few Problems concerning security:

We need a User who has access to all personal files on the file system, who is used for mounting the directories.

The User index_service needs full access to all personal files.

But the main Problems are the system Principals. Every User, who has a Role, that has System Principal right (full read and write access) can access all personal files, that are integrated in a File System Repository. For Example every User, who is a Content-Admin.

Is there an opportunity to restrict access to personal files even to these Users?

Thanks in advance,


Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Sep 19, 2006 at 04:27 AM

    Hi Sven,

    Try setting permissions at the file system level.



    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hello Sven,

      content administrators or other adminstrative need not to be defined by the SAP standard roles (content admin, super admin, etc,.).

      These special roles are defined as principal roles/user/groups.

      Nothing new.

      Why don't you create distributed content administrators or content administrative roles, which are not prinicipals?

      You can use customed roles/groups/user for this reason, without assigneing them to prinicipal rights.

      Not every content manager is supposed to be a prinicipal. Sure it is a organizational question - but it needs to be specified in detail/concepts.



      ps: assign points if it was helpful

      Message was edited by:

      Darijo Pavlic

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.