Bug #4862
closedNCEAS registry form now creates access rules for extra parties
0%
Description
In the past, EML documents created using the NCEAS registry form were written with the following automatic access rules:
ALLOW: [all] uid=nceasadmin,o=NCEAS,dc=ecoinformatics,dc=org
ALLOW: [read][write] [...dn of document submitter...]
ALLOW: [read] public
However, as of approx March 2009, it looks like the following extra access rules are also being added:
ALLOW: [all] cn=knb-prod,o=NCEAS,dc=ecoinformatics,dc=org
ALLOW: [all] cn=esa-moderators,dc=ecoinformatics,dc=org
This doesn't seem right. My guess is that the NCEAS registry has been polluted by rules that are supposed to apply to other registries?
AFAICT, the most recent package created with the original access rules is nceas.955.1, submitted on 26-Feb-2009. The first package created with the extra rules is nceas.956.1, submitted on 31-Mar-2009. Presumably a change was made sometime in between those dates.
Updated by ben leinfelder over 11 years ago
- Status changed from New to Closed
- Assignee changed from Shaun Walbridge to ben leinfelder
This is a configuration issue. I'll remove the ESA entry, but keep the knb-prod entry because we use this same Metacat instance for the KNB registry.