[
https://issues.apache.org/jira/browse/JCR-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16082288#comment-16082288
]
Julian Reschke commented on JCR-4161:
-------------------------------------
http://jackrabbit.apache.org/jcr/mailing-lists.html
> Information on encryption methodology of Jack Rabbit Repository
> ---------------------------------------------------------------
>
> Key: JCR-4161
> URL: https://issues.apache.org/jira/browse/JCR-4161
> Project: Jackrabbit Content Repository
> Issue Type: Task
> Components: jackrabbit-core
> Affects Versions: 2.8
> Reporter: DilipKumar S
> Priority: Critical
> Attachments: DS_JCR_DATASTORE.xlsx, rpt_trace_G6113020170703691222.log
>
>
> We have a Front end API using which the reports would be generated and the
> data will be stored in Jack Rabbit respository table DS_JCR_DATASTORE.
> Currently we are facing an issue under which the report generated with the
> Frontend API is not accessible using open/Save mode with below error appended
> in the logs:
> ===========
> 2017-07-03 15:10:31,462 | ERROR | defaultWIMFileBasedRealm/advisor | | |
> WebContainer : 1 | c.o.r.s.ContentRepositoryService | retrieveReport:
> Exception from the uderlying repository
> javax.jcr.PathNotFoundException: aaa/report/G7893420170703691287
> =============
> Based on the above error, we would like to to do a analysis on whether the
> report generated exists or not with the repository table DS_JCR_DATASTORE,
> but we are restricted from performing the analysis due to below constraint:
> *The records generated and stored with DS_JCR_DATASTORE are in encrypted
> format*
> To do the analysis we need to map the relation between a session_id against a
> record_id in repository table, therefore I request you to let us know *the
> steps to decrypt the encrypted data in the table*.
> I've attached the logs & sample data from DS_JCR_DATASTORE for your reference.
> Please let me know if you require any additional information.
> Thanks & Regards,
> Dilipkumar S
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
