[
https://issues.apache.org/jira/browse/CONNECTORS-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711299#comment-14711299
]
Muhammed Olgun commented on CONNECTORS-1232:
--------------------------------------------
I didn't understand what you mean but basically gets document's ACL and applies
it to RepositoryDocument.
CMIS permissions can be user defined as spec says
http://docs.oasis-open.org/cmis/CMIS/v1.1/os/CMIS-v1.1-os.html#x1-1710002 . So
we don't know which permission is allow, which permission is deny. Because of
that we get this information from job specification page. User gives us
permission informations then we get document ACL, extract its ACEs. If ACE
permissions match allow permission, we add it's principal id to allow array.
Same for deny.
> Add security support on CMIS Repository Connector
> -------------------------------------------------
>
> Key: CONNECTORS-1232
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1232
> Project: ManifoldCF
> Issue Type: Improvement
> Components: CMIS connector
> Reporter: Muhammed Olgun
> Assignee: Muhammed Olgun
> Priority: Minor
> Fix For: ManifoldCF 2.2
>
> Attachments: CONNECTORS-1232.patch
>
>
> I realized that CMIS repository connector doesn't add ACL's to
> RepositoryDocument.
> This patch gets allow and deny permissions from specification page
> (permissions must be comma separated). If CMIS repository supports ACL then
> it includes principals to RepositoryDocument.
> I'll attach a patch. I ran my tests but a review would be great.
> Thanks!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
