[
https://issues.apache.org/jira/browse/OAK-3761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15122006#comment-15122006
]
Timothee Maret commented on OAK-3761:
-------------------------------------
Thanks all for your feedback.
AFAIU, the consensus is that Apache Oak does not need to define its own crypto
API (independently of course of whether it may or may not ships its own
implementation).
All the forecasted crypto related features so far could be implemented either
via the existing hooks (e.g. OAK-3626) or via hooks to be be developed (e.g.
the {{CredentialStore}} API that [~chetanm] described above).
I'll close this issue as won't fix tomorrow and propose a modified version of
the patch to Apache Sling, unless someone come up with legit Oak crypto related
features which can't or should not be implement via hooks.
> Oak crypto API and implementation
> ---------------------------------
>
> Key: OAK-3761
> URL: https://issues.apache.org/jira/browse/OAK-3761
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: security
> Affects Versions: 1.3.12
> Reporter: Timothee Maret
> Assignee: angela
> Attachments: OAK-3761.patch, OAK-3761.patch
>
>
> As discussed in [0], this issue tracks adding a simple API and implementation
> for encryption/decryption in Oak.
> [0]
> http://oak.markmail.org/search/?q=crypto#query:crypto+page:1+mid:iwsfd66lku2dzs2n+state:results
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
