[STANBOL-863] SolrYard needs to access SolrServer using AccessController.doPrivileged

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: entityhub-0.11.0
• Component/s: Entityhub
• Assignee: Rupert Westenthaler
• Reporter: Rupert Westenthaler
• Created: 23/Dec/12 07:11
• Updated: 17/Jul/13 15:14
• Resolved: 23/Dec/12 07:14

Description

The access of Apache Solr to Files in the solr instanceDir is not permitted by the SecurityManager given the permissions of the anonymous user. This results in exceptions such as

Caused by: java.security.AccessControlException: access denied (java.io.FilePermission

{stanbol-working-dir}

/stanbol/indexes/default/entityhub-2012.12.22/data/index.propertiesread)
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:374)
[..]
at java.io.File.exists(File.java:731)
at org.apache.solr.core.SolrCore.getNewIndexDir(SolrCore.java:197)

Typically this appears when adding Documents to the SolrServer. Therefore users will see those Exceptions on calls to store(..), update(..) or remove(..). However internally those exceptions do also appear when storing the namespace prefix map to the SolrServer.

User facing Exceptions will look like

Caused by: org.apache.stanbol.entityhub.servicesapi.yard.YardException:
Exception while adding Document to Solr
at org.apache.stanbol.entityhub.yard.solr.impl.SolrYard.store(SolrYard.java:1170)

resulting in HTTP responses with status 500

Issue Links

• is related to: STANBOL-721 Introduce authentication mechanism