Re: value level encryption

2017-11-03 Thread Justin Edelson
In AEM, posting encrypted properties to /etc/cloudservices is historically the primary use case for @Encrypted, but the PostProcessor applies to all post requests. I think this would be a useful addition to Sling. We may want to have some kind of SPI to support different encryption schemes, but th

RE: value level encryption

2017-11-03 Thread Jason Bailey
They only docs I can find on that, assuming we're talking AEM, mentions it only works for posting things into /etc/cloudservices. So that's out. It's been a while, but I'm under the impression that all implementations of the java platform now come with a certain level of crypto https://docs.orac

Re: value level encryption

2017-11-03 Thread Justin Edelson
We have this in our commercial product. At a high level, the way it works is that there is a PostProcessor which looks for an @Encrypted postfixed property and, if that is present, the corresponding property is stored in an encrypted fashion. Decryption is all done manually, although personally the

[jira] [Commented] (SLING-7226) Repo Init: allow to pass intermediate path upon creating service user

2017-11-03 Thread Timothee Maret (JIRA)
[ https://issues.apache.org/jira/browse/SLING-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237655#comment-16237655 ] Timothee Maret commented on SLING-7226: --- [~anchela] I think it is indeed not support

Re: [svn/git] Whiteboard not writeable anymore

2017-11-03 Thread Carsten Ziegeler
I've moved the new feature model from svn to the git whiteboard now Carsten Carsten Ziegeler wrote > Thanks Bertrand. > > I don't think we need history. > > I've created > > https://github.com/apache/sling-whiteboard > > and I guess we don't need to move everything over from svn either. If >

Re: [svn/git] Whiteboard not writeable anymore

2017-11-03 Thread Carsten Ziegeler
Thanks Bertrand. I don't think we need history. I've created https://github.com/apache/sling-whiteboard and I guess we don't need to move everything over from svn either. If something is needed we can move it on demand. Regards Carsten Bertrand Delacretaz wrote > Hi, > > On Fri, Nov 3, 201

[jira] [Resolved] (SLING-7229) DistributionAgentServlet throws NPE upon test action

2017-11-03 Thread Timothee Maret (JIRA)
[ https://issues.apache.org/jira/browse/SLING-7229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothee Maret resolved SLING-7229. --- Resolution: Fixed > DistributionAgentServlet throws NPE upon test action > ---

[jira] [Commented] (SLING-7229) DistributionAgentServlet throws NPE upon test action

2017-11-03 Thread Timothee Maret (JIRA)
[ https://issues.apache.org/jira/browse/SLING-7229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237618#comment-16237618 ] Timothee Maret commented on SLING-7229: --- Fixed in https://github.com/apache/sling-o

Re: [svn/git] Whiteboard not writeable anymore

2017-11-03 Thread Bertrand Delacretaz
Hi, On Fri, Nov 3, 2017 at 2:02 PM, Carsten Ziegeler wrote: > ...Any plans to > move this as a single project to git?... I think a sling-whiteboard Git repo is useful. Moving the existing code without history is probably good enough, or we can ask infra to convert it. If we don't need history

[svn/git] Whiteboard not writeable anymore

2017-11-03 Thread Carsten Ziegeler
Hi, I guess we discussed this during the move to git discussions, but currently the whiteboard is still in svn and not writeable. Any plans to move this as a single project to git? Or what is our approach? Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org

value level encryption

2017-11-03 Thread Jason Bailey
Here's the use case My organization has decided that to conform to the GDPR, any sensitive data should be encrypted while at rest. From a Sling perspective that is a challenge since we've empowered the authors to create forms the way they want. So to be on the safe side, we're looking at encryp

Re: [VOTE] Release Apache Sling API 2.16.4, JCR Resource Resolver 3.0.6, Default GET Servlets 2.1.29

2017-11-03 Thread Karl Pauls
+1 regards, Karl On Fri, Nov 3, 2017 at 10:40 AM, Antonio Sanso wrote: > +1 > > On Nov 2, 2017, at 5:49 PM, Ian Boston wrote: > >> Hi, >> >> I would like to call a vote on the following release, >> >> Apache Sling API 2.16.4 >> Apache Sling JCR Resource Resolver 3.0.6 >> Apache Sling Default G

[jira] [Created] (SLING-7229) DistributionAgentServlet throws NPE upon test action

2017-11-03 Thread Timothee Maret (JIRA)
Timothee Maret created SLING-7229: - Summary: DistributionAgentServlet throws NPE upon test action Key: SLING-7229 URL: https://issues.apache.org/jira/browse/SLING-7229 Project: Sling Issue Ty

Re: [VOTE] Release Apache Sling API 2.16.4, JCR Resource Resolver 3.0.6, Default GET Servlets 2.1.29

2017-11-03 Thread Antonio Sanso
+1 On Nov 2, 2017, at 5:49 PM, Ian Boston wrote: > Hi, > > I would like to call a vote on the following release, > > Apache Sling API 2.16.4 > Apache Sling JCR Resource Resolver 3.0.6 > Apache Sling Default GET Servlets 2.1.29 > > We solved 11 issue in this release: > *https://issues.apache.o

Re: [VOTE] Release Apache Sling Service User Mapper 1.3.6

2017-11-03 Thread Antonio Sanso
+1 On Nov 2, 2017, at 5:15 PM, Karl Pauls wrote: > I would like to call a vote on the following release, > > Apache Sling Service User Mapper 1.3.6 > > We solved 2 issue in this release: > https://issues.apache.org/jira/projects/SLING/versions/12341841 > > Staging repository: > https://reposit

Re: [VOTE] Release Apache Sling API 2.16.4, JCR Resource Resolver 3.0.6, Default GET Servlets 2.1.29

2017-11-03 Thread Carsten Ziegeler
+1 for all three releases The version of servlets get is 2.1.28 (not 2.1.29) Carsten Ian Boston wrote > Hi, > > I would like to call a vote on the following release, > > Apache Sling API 2.16.4 > Apache Sling JCR Resource Resolver 3.0.6 > Apache Sling Default GET Servlets 2.1.29 > > We solve

Re: [VOTE] Release Apache Sling Service User Mapper 1.3.6

2017-11-03 Thread Carsten Ziegeler
+1 Karl Pauls wrote > I would like to call a vote on the following release, > > Apache Sling Service User Mapper 1.3.6 > > We solved 2 issue in this release: > https://issues.apache.org/jira/projects/SLING/versions/12341841 > > Staging repository: > https://repository.apache.org/content/reposi