Hello,

I'm having an issue when trying to ingest a simple FOXML (example) that looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<foxml:digitalObject VERSION="1.1" PID="cellar:209" xmlns:foxml="info:fedora/fedora-system:def/foxml#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="info:fedora/fedora-system:def/foxml# http://www.fedora.info/definitions/1/0/foxml1-1.xsd">
<foxml:objectProperties>
<foxml:property NAME="info:fedora/fedora-system:def/model#state" VALUE="Active"/>
<foxml:property NAME="info:fedora/fedora-system:def/model#label" VALUE="manifestation"/>
</foxml:objectProperties>
<foxml:datastream ID="DOC_1" STATE="A" CONTROL_GROUP="M" VERSIONABLE="true">
    <foxml:datastreamVersion ID="DOC_1.0" LABEL="DOC_1"  MIMETYPE="text/plain">
            <foxml:contentLocation REF="file:///file.txt" TYPE="URL"/>
    </foxml:datastreamVersion>
</foxml:datastream>
</foxml:digitalObject>

In this example, I'm trying to ingest a digital file with one datastream that should contain one digital file (file.txt).

When running this command:

   ./fedora-ingest.sh f sample-foxml.xml info:fedora/fedora-system:FOXML-1.1 localhost:8080 [username] [userpassword] http

I'm getting the exception:

Error  : org.fcrepo.server.errors.HttpServiceNotFoundException: [DefaultExternalContentManager] returned an error.  The underlying error was a org.fcrepo.server.errors.HttpServiceNotFoundException  The message was  "Policy blocked datastream resolution"

I did change the server policy as described on: https://wiki.duraspace.org/display/FCR30/Ingest+with+the+file+URI+scheme

Once the policy is changed (in data/fedora-xacml-policies/repository-policies/default/), I'm getting an error when running this command:

   ./fedora-reload-policies.sh reloadpolicies  http [username] [userpassword]

   java.io.IOException: Request failed [403 Forbidden]

So unfortunately, it fails to reload the policies.

I have tried many things but none of them actually work. I'm still getting Policy blocked datastream resolution. Is there something I missed or doing wrong?

Environment:
We don't have this problem on local developers' machines running on Windows.

Thanks in advance.

Kind regards,

--
Ludovic