Morpho

Are you checking the access rules on the CN or the MN? Updates to the access policy are made to the CN for packages that are saved to the network.

Good question. I checked the access policy on the MN. I just checked the cn. The data package identifier doesn't exist at all.

My cn url is https://cn.dataone.org/cn and my mn url is https://mn-demo-5.test.dataone.org/knb/d1/mn

I don't think the mn is part of this cn. So the change the access policy should fail. But morpho says it succeeded.

I tried this with the same set-up you describe, but get an error message about the object not being on the CN (as expected):

urn:uuid:6bdb98da-907f-4e8c-9480-a69c79fc4ba8 not found on the Coordinating Node. Cannot set Access Policy until it has been synchronized. Please try again later.

What could the difference be between our set-ups?

I just created a package by the new data package wizard and saved it to the network. Then I added a new rule and it said:
Successfully set Access Policy for tao.2013021216283490594

in preference dialog, it shows:

https://mn-demo-5.test.dataone.org/knb/d1/mn
https://cn.dataone.org/cn

The boolean operation when calling local vs. network was short circuiting when it was network-only and not even calling the network method. No exception was thrown and the return status wasn't being checked (nor was it correct).
Fixed all of this for both access policy and replication policy.

Original Bugzilla ID was 5856