[
https://issues.apache.org/jira/browse/JCR-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15633074#comment-15633074
]
angela commented on JCR-4050:
-----------------------------
[~bornemannjs], thanks for the insights. on the documentation you state that
you were evaluating different ways of synchronizing repository content between
different instances and that WebDAV was not found to be efficient. Did you also
evaluate the JCR-remoting with it's extension that allows to process large
chunks of content with a single request? It has been improved recently by
[~alfu] allowing to transport protected content (access control content to be
precise) in a way that would allow to easily expand that to other protected
items such as those stored with user/group content.
While I see the point of your extension, my gut feeling tells me that this
doesn't belong to the API contract... trying to explore other possibilities
that would allow you to efficiently synchronizing your data.
> Allow creation of users with existing password hashes in UserManager
> ---------------------------------------------------------------------
>
> Key: JCR-4050
> URL: https://issues.apache.org/jira/browse/JCR-4050
> Project: Jackrabbit Content Repository
> Issue Type: New Feature
> Components: jackrabbit-api, jackrabbit-core, security
> Reporter: Jeffrey Bornemann
> Priority: Minor
>
> We utilize the UserManager API within Grabbit for syncing authorizable nodes
> between servers.
> Unfortunately, when it comes to syncing users, and specifically setting
> passwords from existing users; we have no public API facing way to create
> users with existing password hashes. We currently have to resort to using
> reflection, grabbing internal tree objects, and a bunch of nastiness that we
> would love to avoid with this change.
> Other consumers may also find this useful.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
