[jira] [Updated] (OAK-8117) NPE when adding ACE with restrictions and remapped namespaces
[
https://issues.apache.org/jira/browse/OAK-8117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-8117:
--
Fix Version/s: (was: 1.11.0)
> NPE when adding ACE with restrictions and remapped namespaces
> -
>
> Key: OAK-8117
> URL: https://issues.apache.org/jira/browse/OAK-8117
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, security
>Reporter: angela
>Assignee: angela
>Priority: Major
> Fix For: 1.12.0
>
> Attachments: OAK-8117-test.patch, OAK-8117.patch
>
>
> [~stillalex], just ran into an NPE when adding an ACE including some
> restriction. The reason is a tiny bug in the {{ACL}} implementation that
> mistakenly uses the _oakName_ to retrieve the value/values from the passed
> restriction map. It should obviously use the key of the map, which
> corresponds to the _jcrName_. in other words: the bug only shows up when
> running tests with re-mapped namespaces.
> proposed fix attached. will attach a test case illustrating the issue later
> on.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-8117) NPE when adding ACE with restrictions and remapped namespaces
[
https://issues.apache.org/jira/browse/OAK-8117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated OAK-8117:
Attachment: OAK-8117-test.patch
> NPE when adding ACE with restrictions and remapped namespaces
> -
>
> Key: OAK-8117
> URL: https://issues.apache.org/jira/browse/OAK-8117
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, security
>Reporter: angela
>Assignee: angela
>Priority: Major
> Attachments: OAK-8117-test.patch, OAK-8117.patch
>
>
> [~stillalex], just ran into an NPE when adding an ACE including some
> restriction. The reason is a tiny bug in the {{ACL}} implementation that
> mistakenly uses the _oakName_ to retrieve the value/values from the passed
> restriction map. It should obviously use the key of the map, which
> corresponds to the _jcrName_. in other words: the bug only shows up when
> running tests with re-mapped namespaces.
> proposed fix attached. will attach a test case illustrating the issue later
> on.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-8117) NPE when adding ACE with restrictions and remapped namespaces
[
https://issues.apache.org/jira/browse/OAK-8117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated OAK-8117:
Fix Version/s: 1.11.0
1.12
> NPE when adding ACE with restrictions and remapped namespaces
> -
>
> Key: OAK-8117
> URL: https://issues.apache.org/jira/browse/OAK-8117
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, security
>Reporter: angela
>Assignee: angela
>Priority: Major
> Fix For: 1.12, 1.11.0
>
> Attachments: OAK-8117-test.patch, OAK-8117.patch
>
>
> [~stillalex], just ran into an NPE when adding an ACE including some
> restriction. The reason is a tiny bug in the {{ACL}} implementation that
> mistakenly uses the _oakName_ to retrieve the value/values from the passed
> restriction map. It should obviously use the key of the map, which
> corresponds to the _jcrName_. in other words: the bug only shows up when
> running tests with re-mapped namespaces.
> proposed fix attached. will attach a test case illustrating the issue later
> on.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-8117) NPE when adding ACE with restrictions and remapped namespaces
[
https://issues.apache.org/jira/browse/OAK-8117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated OAK-8117:
Attachment: OAK-8117.patch
> NPE when adding ACE with restrictions and remapped namespaces
> -
>
> Key: OAK-8117
> URL: https://issues.apache.org/jira/browse/OAK-8117
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, security
>Reporter: angela
>Assignee: angela
>Priority: Major
> Attachments: OAK-8117.patch
>
>
> [~stillalex], just ran into an NPE when adding an ACE including some
> restriction. The reason is a tiny bug in the {{ACL}} implementation that
> mistakenly uses the _oakName_ to retrieve the value/values from the passed
> restriction map. It should obviously use the key of the map, which
> corresponds to the _jcrName_. in other words: the bug only shows up when
> running tests with re-mapped namespaces.
> proposed fix attached. will attach a test case illustrating the issue later
> on.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
