[jira] [Commented] (OAK-7182) Make it possible to update Guava

2018-04-18 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-7182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442475#comment-16442475
 ] 

Julian Reschke commented on OAK-7182:
-

[~rombert] - I had a look at your suggestions wrt "".

I tried this with oak-core-spi:
{noformat}
Index: pom.xml
===
--- pom.xml (revision 1829432)
+++ pom.xml (working copy)
@@ -35,10 +35,7 @@
 maven-bundle-plugin
 
   
-
-  ${guava.osgi.import},
-  *
-
+com.google.*
 
   org.apache.jackrabbit.oak.cache,
   org.apache.jackrabbit.oak.commons.jmx,
{noformat}

As predicted in 
,
 I'm getting warnings as we use Guava APIs in exported method signatures: 
{noformat}
[WARNING] Bundle org.apache.jackrabbit:oak-core-spi:bundle:1.10-SNAPSHOT : 
Export org.apache.jackrabbit.oak.cache,  has 2,  private references 
[com.google.common.cache, com.google.common.collect],
[WARNING] Bundle org.apache.jackrabbit:oak-core-spi:bundle:1.10-SNAPSHOT : 
Export org.apache.jackrabbit.oak.commons.jmx,  has 1,  private references 
[com.google.common.base],
[WARNING] Bundle org.apache.jackrabbit:oak-core-spi:bundle:1.10-SNAPSHOT : 
Export org.apache.jackrabbit.oak.spi.whiteboard,  has 1,  private references 
[com.google.common.base],
{noformat}

Also, JAR file size for oak-core-spi goes up from 152087 to 1950807 (with Guava 
15).

> Make it possible to update Guava
> 
>
> Key: OAK-7182
> URL: https://issues.apache.org/jira/browse/OAK-7182
> Project: Jackrabbit Oak
>  Issue Type: Wish
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Attachments: OAK-7182-guava-21.diff, guava.diff
>
>
> We currently rely on Guava 15, and this affects all users of Oak because they 
> essentially need to use the same version.
> This is an overall issue to investigate what would need to be done in Oak in 
> order to make updates possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7417) Build Jackrabbit Oak #1379 failed

2018-04-18 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-7417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442458#comment-16442458
 ] 

Hudson commented on OAK-7417:
-

Previously failing build now is OK.
 Passed run: [Jackrabbit Oak 
#1381|https://builds.apache.org/job/Jackrabbit%20Oak/1381/] [console 
log|https://builds.apache.org/job/Jackrabbit%20Oak/1381/console]

> Build Jackrabbit Oak #1379 failed
> -
>
> Key: OAK-7417
> URL: https://issues.apache.org/jira/browse/OAK-7417
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit Oak #1379 has failed.
> First failed run: [Jackrabbit Oak 
> #1379|https://builds.apache.org/job/Jackrabbit%20Oak/1379/] [console 
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1379/console]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7421) link Guava javadoc

2018-04-18 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-7421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442367#comment-16442367
 ] 

Julian Reschke commented on OAK-7421:
-

trunk: [r1829432|http://svn.apache.org/r1829432]


> link Guava javadoc
> --
>
> Key: OAK-7421
> URL: https://issues.apache.org/jira/browse/OAK-7421
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Fix For: 1.9.0, 1.10
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (OAK-7421) link Guava javadoc

2018-04-18 Thread Julian Reschke (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-7421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke resolved OAK-7421.
-
Resolution: Fixed

> link Guava javadoc
> --
>
> Key: OAK-7421
> URL: https://issues.apache.org/jira/browse/OAK-7421
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Fix For: 1.9.0, 1.10
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (OAK-7421) link Guava javadoc

2018-04-18 Thread Julian Reschke (JIRA) 
Julian Reschke created OAK-7421:
---

 Summary: link Guava javadoc
 Key: OAK-7421
 URL: https://issues.apache.org/jira/browse/OAK-7421
 Project: Jackrabbit Oak
  Issue Type: Task
  Components: parent
Reporter: Julian Reschke
Assignee: Julian Reschke
 Fix For: 1.10






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-7421) link Guava javadoc

2018-04-18 Thread Julian Reschke (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-7421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated OAK-7421:

Fix Version/s: 1.9.0

> link Guava javadoc
> --
>
> Key: OAK-7421
> URL: https://issues.apache.org/jira/browse/OAK-7421
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Fix For: 1.9.0, 1.10
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7416) Contribute a 'proc' subtree for the Segment Node Store

2018-04-18 Thread Francesco Mari (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-7416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442358#comment-16442358
 ] 

Francesco Mari commented on OAK-7416:
-

If there are no objections, I will commit the proc tree in trunk tomorrow.

> Contribute a 'proc' subtree for the Segment Node Store
> --
>
> Key: OAK-7416
> URL: https://issues.apache.org/jira/browse/OAK-7416
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
>Priority: Major
>  Labels: tooling
> Fix For: 1.10
>
>
> With guidance from [~mduerig], I recently developed a way to expose Segment 
> Node Store's internal information through the NodeState API. 
> The concept is similar in spirit to the proc file system in Linux: the proc 
> subtree exposes internal information in a straightforward manner, enabling 
> consumers to rely on a well-understood API to access the data. This proc 
> subtree shelters tooling from variations of the internal APIs of the Segment 
> Store. As long as the data exported through the proc subtree is stable, the 
> same tools are going to work across different versions of the Segment Store 
> with minimal to no modifications.
> The proc subtree has been developed in [this branch on 
> GitHub|https://github.com/francescomari/jackrabbit-oak/tree/proc]. I created 
> this issue in order to review the work done so far, and to track the 
> contribution of the proc subtree in Oak.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7416) Contribute a 'proc' subtree for the Segment Node Store

2018-04-18 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/OAK-7416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442355#comment-16442355
 ] 

Michael Dürig commented on OAK-7416:


bq.  I think that this is better tackled in one or more follow-up issues.

ack

> Contribute a 'proc' subtree for the Segment Node Store
> --
>
> Key: OAK-7416
> URL: https://issues.apache.org/jira/browse/OAK-7416
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
>Priority: Major
>  Labels: tooling
> Fix For: 1.10
>
>
> With guidance from [~mduerig], I recently developed a way to expose Segment 
> Node Store's internal information through the NodeState API. 
> The concept is similar in spirit to the proc file system in Linux: the proc 
> subtree exposes internal information in a straightforward manner, enabling 
> consumers to rely on a well-understood API to access the data. This proc 
> subtree shelters tooling from variations of the internal APIs of the Segment 
> Store. As long as the data exported through the proc subtree is stable, the 
> same tools are going to work across different versions of the Segment Store 
> with minimal to no modifications.
> The proc subtree has been developed in [this branch on 
> GitHub|https://github.com/francescomari/jackrabbit-oak/tree/proc]. I created 
> this issue in order to review the work done so far, and to track the 
> contribution of the proc subtree in Oak.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7416) Contribute a 'proc' subtree for the Segment Node Store

2018-04-18 Thread Francesco Mari (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-7416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442345#comment-16442345
 ] 

Francesco Mari commented on OAK-7416:
-

[~mduerig], I merged the PR. Not only the package lacks Javadoc, but the proc 
tree needs to be described in our documentation. I think that this is better 
tackled in one or more follow-up issues.

> Contribute a 'proc' subtree for the Segment Node Store
> --
>
> Key: OAK-7416
> URL: https://issues.apache.org/jira/browse/OAK-7416
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
>Priority: Major
>  Labels: tooling
> Fix For: 1.10
>
>
> With guidance from [~mduerig], I recently developed a way to expose Segment 
> Node Store's internal information through the NodeState API. 
> The concept is similar in spirit to the proc file system in Linux: the proc 
> subtree exposes internal information in a straightforward manner, enabling 
> consumers to rely on a well-understood API to access the data. This proc 
> subtree shelters tooling from variations of the internal APIs of the Segment 
> Store. As long as the data exported through the proc subtree is stable, the 
> same tools are going to work across different versions of the Segment Store 
> with minimal to no modifications.
> The proc subtree has been developed in [this branch on 
> GitHub|https://github.com/francescomari/jackrabbit-oak/tree/proc]. I created 
> this issue in order to review the work done so far, and to track the 
> contribution of the proc subtree in Oak.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-7420) Introduce SegmentNodeStoreMonitoringService for exposing writerGroups as an OSGi config property

2018-04-18 Thread Andrei Dulceanu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-7420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrei Dulceanu updated OAK-7420:
-
Summary: Introduce SegmentNodeStoreMonitoringService for exposing 
writerGroups as an OSGi config property  (was: Introduce 
SegmentNodeStoreMonitoringService for exposing writerGroups as OSGi config 
property)

> Introduce SegmentNodeStoreMonitoringService for exposing writerGroups as an 
> OSGi config property
> 
>
> Key: OAK-7420
> URL: https://issues.apache.org/jira/browse/OAK-7420
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: segment-tar
>Reporter: Andrei Dulceanu
>Assignee: Andrei Dulceanu
>Priority: Minor
>  Labels: tooling
> Fix For: 1.9.0, 1.10
>
>
> It would be useful to expose {{writerGroups}} in {{SegmentNodeStoreStats}} 
> through an OSGi config property. Since this is a low level configuration 
> related to monitoring, it shouldn't be added to {{SegmentNodeStoreService}}, 
> but to a newly created service, {{SegmentNodeStoreMonitoringService}} that 
> would handle exposing monitoring related stuff. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (OAK-7420) Introduce SegmentNodeStoreMonitoringService for exposing writerGroups as OSGi config property

2018-04-18 Thread Andrei Dulceanu (JIRA) 
Andrei Dulceanu created OAK-7420:


 Summary: Introduce SegmentNodeStoreMonitoringService for exposing 
writerGroups as OSGi config property
 Key: OAK-7420
 URL: https://issues.apache.org/jira/browse/OAK-7420
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: segment-tar
Reporter: Andrei Dulceanu
Assignee: Andrei Dulceanu
 Fix For: 1.9.0, 1.10


It would be useful to expose {{writerGroups}} in {{SegmentNodeStoreStats}} 
through an OSGi config property. Since this is a low level configuration 
related to monitoring, it shouldn't be added to {{SegmentNodeStoreService}}, 
but to a newly created service, {{SegmentNodeStoreMonitoringService}} that 
would handle exposing monitoring related stuff. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7217) check public Oak APIs for references to Guava

2018-04-18 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442250#comment-16442250
 ] 

Julian Reschke commented on OAK-7217:
-

See 


> check public Oak APIs for references to Guava
> -
>
> Key: OAK-7217
> URL: https://issues.apache.org/jira/browse/OAK-7217
> Project: Jackrabbit Oak
>  Issue Type: Technical task
>Reporter: Julian Reschke
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7416) Contribute a 'proc' subtree for the Segment Node Store

2018-04-18 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/OAK-7416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442242#comment-16442242
 ] 

Michael Dürig commented on OAK-7416:


[~frm], I just went to the proposed changes. This looks very good to me and I'd 
be +1 to applying  this in trunk.
 * See [https://github.com/francescomari/jackrabbit-oak/pull/18/files] for some 
proposed changes to clean up a few bits.
 * The classes in {{org.apache.jackrabbit.oak.segment.file.proc}} generally 
lack Javadoc. No blocker for trunk, but let's add some class level comments re. 
what the structure of what the individual classes as long as our memories are 
still fresh.

> Contribute a 'proc' subtree for the Segment Node Store
> --
>
> Key: OAK-7416
> URL: https://issues.apache.org/jira/browse/OAK-7416
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
>Priority: Major
>  Labels: tooling
> Fix For: 1.10
>
>
> With guidance from [~mduerig], I recently developed a way to expose Segment 
> Node Store's internal information through the NodeState API. 
> The concept is similar in spirit to the proc file system in Linux: the proc 
> subtree exposes internal information in a straightforward manner, enabling 
> consumers to rely on a well-understood API to access the data. This proc 
> subtree shelters tooling from variations of the internal APIs of the Segment 
> Store. As long as the data exported through the proc subtree is stable, the 
> same tools are going to work across different versions of the Segment Store 
> with minimal to no modifications.
> The proc subtree has been developed in [this branch on 
> GitHub|https://github.com/francescomari/jackrabbit-oak/tree/proc]. I created 
> this issue in order to review the work done so far, and to track the 
> contribution of the proc subtree in Oak.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7417) Build Jackrabbit Oak #1379 failed

2018-04-18 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-7417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442229#comment-16442229
 ] 

Hudson commented on OAK-7417:
-

Build is still failing.
Failed run: [Jackrabbit Oak 
#1380|https://builds.apache.org/job/Jackrabbit%20Oak/1380/] [console 
log|https://builds.apache.org/job/Jackrabbit%20Oak/1380/console]

> Build Jackrabbit Oak #1379 failed
> -
>
> Key: OAK-7417
> URL: https://issues.apache.org/jira/browse/OAK-7417
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit Oak #1379 has failed.
> First failed run: [Jackrabbit Oak 
> #1379|https://builds.apache.org/job/Jackrabbit%20Oak/1379/] [console 
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1379/console]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (OAK-7419) SecurityProviderRegistration should only bind configurations defined as required

2018-04-18 Thread Alex Deparvu (JIRA) 
Alex Deparvu created OAK-7419:
-

 Summary: SecurityProviderRegistration should only bind 
configurations defined as required
 Key: OAK-7419
 URL: https://issues.apache.org/jira/browse/OAK-7419
 Project: Jackrabbit Oak
  Issue Type: Task
  Components: core, security
Reporter: Alex Deparvu
Assignee: Alex Deparvu


It can happen that the registration eagerly binds to a configuration deployed 
in the system even though it might not be needed or wanted.
I suggest that the registration only binds to pids defined in the required 
config.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7418) SecurityProviderBuilder ignores configuration option authorizationCompositionType

2018-04-18 Thread Alex Deparvu (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-7418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442194#comment-16442194
 ] 

Alex Deparvu commented on OAK-7418:
---

+1 looks good

> SecurityProviderBuilder ignores configuration option 
> authorizationCompositionType
> -
>
> Key: OAK-7418
> URL: https://issues.apache.org/jira/browse/OAK-7418
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: core, security
>Reporter: angela
>Assignee: angela
>Priority: Minor
> Attachments: OAK-7418.patch
>
>
> For test purpose it would be good to be able to make use of the 
> {{authorizationCompositionType}} configuration option but it seems that 
> {{SecurityProviderBuilder}} ignores it.
> [~stillalex], fyi.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7418) SecurityProviderBuilder ignores configuration option authorizationCompositionType

2018-04-18 Thread angela (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-7418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442029#comment-16442029
 ] 

angela commented on OAK-7418:
-

[~stillalex], proposed patch attached. let me know if it looks reasonable to 
you.

> SecurityProviderBuilder ignores configuration option 
> authorizationCompositionType
> -
>
> Key: OAK-7418
> URL: https://issues.apache.org/jira/browse/OAK-7418
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: core, security
>Reporter: angela
>Assignee: angela
>Priority: Minor
> Attachments: OAK-7418.patch
>
>
> For test purpose it would be good to be able to make use of the 
> {{authorizationCompositionType}} configuration option but it seems that 
> {{SecurityProviderBuilder}} ignores it.
> [~stillalex], fyi.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-7418) SecurityProviderBuilder ignores configuration option authorizationCompositionType

2018-04-18 Thread angela (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-7418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

angela updated OAK-7418:

Attachment: OAK-7418.patch

> SecurityProviderBuilder ignores configuration option 
> authorizationCompositionType
> -
>
> Key: OAK-7418
> URL: https://issues.apache.org/jira/browse/OAK-7418
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: core, security
>Reporter: angela
>Assignee: angela
>Priority: Minor
> Attachments: OAK-7418.patch
>
>
> For test purpose it would be good to be able to make use of the 
> {{authorizationCompositionType}} configuration option but it seems that 
> {{SecurityProviderBuilder}} ignores it.
> [~stillalex], fyi.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (OAK-7418) SecurityProviderBuilder ignores configuration option authorizationCompositionType

2018-04-18 Thread angela (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-7418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

angela reassigned OAK-7418:
---

Assignee: angela

> SecurityProviderBuilder ignores configuration option 
> authorizationCompositionType
> -
>
> Key: OAK-7418
> URL: https://issues.apache.org/jira/browse/OAK-7418
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: core, security
>Reporter: angela
>Assignee: angela
>Priority: Minor
>
> For test purpose it would be good to be able to make use of the 
> {{authorizationCompositionType}} configuration option but it seems that 
> {{SecurityProviderBuilder}} ignores it.
> [~stillalex], fyi.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-7418) SecurityProviderBuilder ignores configuration option authorizationCompositionType

2018-04-18 Thread angela (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-7418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

angela updated OAK-7418:

Priority: Minor  (was: Major)

> SecurityProviderBuilder ignores configuration option 
> authorizationCompositionType
> -
>
> Key: OAK-7418
> URL: https://issues.apache.org/jira/browse/OAK-7418
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: core, security
>Reporter: angela
>Priority: Minor
>
> For test purpose it would be good to be able to make use of the 
> {{authorizationCompositionType}} configuration option but it seems that 
> {{SecurityProviderBuilder}} ignores it.
> [~stillalex], fyi.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-7418) SecurityProviderBuilder ignores configuration option authorizationCompositionType

2018-04-18 Thread angela (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-7418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

angela updated OAK-7418:

Issue Type: Improvement  (was: Bug)

> SecurityProviderBuilder ignores configuration option 
> authorizationCompositionType
> -
>
> Key: OAK-7418
> URL: https://issues.apache.org/jira/browse/OAK-7418
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: core, security
>Reporter: angela
>Priority: Major
>
> For test purpose it would be good to be able to make use of the 
> {{authorizationCompositionType}} configuration option but it seems that 
> {{SecurityProviderBuilder}} ignores it.
> [~stillalex], fyi.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (OAK-7418) SecurityProviderBuilder ignores configuration option authorizationCompositionType

2018-04-18 Thread angela (JIRA) 
angela created OAK-7418:
---

 Summary: SecurityProviderBuilder ignores configuration option 
authorizationCompositionType
 Key: OAK-7418
 URL: https://issues.apache.org/jira/browse/OAK-7418
 Project: Jackrabbit Oak
  Issue Type: Bug
  Components: core, security
Reporter: angela


For test purpose it would be good to be able to make use of the 
{{authorizationCompositionType}} configuration option but it seems that 
{{SecurityProviderBuilder}} ignores it.

[~stillalex], fyi.





--
This message was sent by Atlassian JIRA
(v7.6.3#76005)