[ 
https://issues.apache.org/jira/browse/CONNECTORS-886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894952#comment-13894952
 ] 

Karl Wright commented on CONNECTORS-886:
----------------------------------------

Just some food for thought.

The methods in RepositoryDocument that were meant to handle this kind of thing 
are the following:

{code}
  /** Clear all directory acls. */
  public void clearDirectoryACLs()
  {
    directorySecurity.clear();
  }

  /** Get a count of directory security entries. */
  public int countDirectoryACLs()
  {
    return directorySecurity.size();
  }

  /** Add directory security entry */
  public void addDirectoryACLs(String[] allowACL, String[] denyACL)
  {
    Security s = new Security();
    s.setACL(allowACL);
    s.setDenyACL(denyACL);
    directorySecurity.add(s);
  }

  /** Get directory security access acl */
  public String[] getDirectoryACL(int index)
  {
    Security s = directorySecurity.get(index);
    return s.getACL();
  }

  /** Get directory security deny acl */
  public String[] getDirectoryDenyACL(int index)
  {
    Security s = directorySecurity.get(index);
    return s.getDenyACL();
  }

{code}

Instead of adding "parent" methods in addition to these, I would suggest adding 
either zero or one "directory" set of acls.  Then, maybe modify the Solr plugin 
to be able to work with up to N such directory acls (configurable).  That would 
be a lot closer to the original idea.

Also, you WILL need to support this for Solr 3.x plugin and ElasticSearch.

Thanks!

> Add support for Parent folder security
> --------------------------------------
>
>                 Key: CONNECTORS-886
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-886
>             Project: ManifoldCF
>          Issue Type: Improvement
>          Components: JCIFS connector, Solr-4.x-component
>            Reporter: Shinichiro Abe
>             Fix For: ManifoldCF 1.6
>
>         Attachments: CONNECTORS-886-forSolrPlugin.patch, CONNECTORS-886.patch
>
>
> Windows server checks the access permission of a share folder and the 
> security permission of a file document when we access a file via network.
> As far as I look into that, Windows does not take subfolder's security 
> permissions into account.
> There is a case that someone who is admin wants to configure 'Everyone' for 
> 'share folders' and configure each access permissions for 'sub folders'.
> E.g. \\ShareFolder\Admin --> Admin folder for administrative user,  
> \\ShareFolder\Sales  --> Sales folder for sales user.
> The users put files in 'sub folders', then the permission of these files will 
> be inherited from the permission of 'sub folders'.
> I'd like to support access permissions for 'sub folders' in jcifs/solr 
> connector.
> In general, we expect file's permission to be inherited from parent folder.
> So I want to manage parent's security by providing new [allow|deny]_token 
> fields.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to