[
https://issues.apache.org/jira/browse/OAK-3761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115082#comment-15115082
]
Chetan Mehrotra commented on OAK-3761:
--------------------------------------
bq. G0. Allow to unprotect OSGI configuration properties on demand
Yes that was the usecase I had in mind for this issue.
bq. G1. Add support for a general crypto API
This is an interesting usecase. So far not seen a strong requirement for such a
feature but would be good to have one. Key thing that Oak provides an extension
hook on which this can be build. For e.g. this can be done today also via
having a custom CommitHook which can manipulate the NodeBuilder state upon
commit and replace sensitive property state. May be some explicit entry point
need to be provided. So not sure
So I would say lets aim first for OAK-3626 as we have consensus for that. For
other we can have a thread on mailing list. I think couple CryptoService with
Oak might slowdown this stuff and unnecessarily tie it to Oak release cycle
(with all branching overhead). It can live independently and more suitable
place for that would be Sling!. Again no issues with crypto feature at all ...
just trying to find the right place where such a feature should live
> 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)
