[
https://issues.apache.org/jira/browse/JCRVLT-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCRVLT-63:
-------------------------
Description:
upon user/group import the DocViewSAXImporter relies on the jackrabbit 2.x
implementation that the authorizable id is encoded in the name of the
corresponding node.
since oak 1.0 however this can be customized and there is no guarantee that the
node name reveals the authorizable id (see
http://jackrabbit.apache.org/oak/docs/security/user.html). in order to keep
fvault compatible with oak this should be fixed.
proposed (but untested) patch attached.
was:
upon user/group import the DocViewSAXImporter relies on the jackrabbit 2.x
implementation that the authorizable id is encoded in the name of the
corresponding node.
since oak 1.0 however this can be customized and there is no guarantee that the
node name reveals the authorizable id. in order to keep fvault compatible with
oak this should be fixed.
proposed (but untested) patch attached.
> DocViewSAXImporter relies on implementation detail wrt authorizable Id
> ----------------------------------------------------------------------
>
> Key: JCRVLT-63
> URL: https://issues.apache.org/jira/browse/JCRVLT-63
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Reporter: angela
> Attachments: JCRVLT-63.patch
>
>
> upon user/group import the DocViewSAXImporter relies on the jackrabbit 2.x
> implementation that the authorizable id is encoded in the name of the
> corresponding node.
> since oak 1.0 however this can be customized and there is no guarantee that
> the node name reveals the authorizable id (see
> http://jackrabbit.apache.org/oak/docs/security/user.html). in order to keep
> fvault compatible with oak this should be fixed.
> proposed (but untested) patch attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
