Story #6296: authMN SM.accessPolicy out of synch with CN and replicaMN
Call CN.setAccessPolicy() whenever access control rules are updated in Metacat
When EML is processed and access control rules within it are added to Metacat, these changes should be submitted to the CN.
The action=setaccess Metacat servlet API is another point where the access policy can be manipulated.
Starting point for looking at this behavior (in main Metacat project):
#2 Updated by ben leinfelder almost 7 years ago
- Estimated time set to 0.00 h
- Status changed from Resolved to In Progress
I like the approach in EML210SAXHandler for synching the data pids after the transaction has been committed. I think the EML200SAXHandler also needs similar logic since we still technically support that version of EML even if its access control rules are defined slightly differently. Both versions can control access rules on data objects stored in Metacat so it's important that they are treated the same.