Project

General

Profile

Bug #4862

NCEAS registry form now creates access rules for extra parties

Added by Jim Regetz over 9 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Category:
registry
Target version:
Start date:
03/02/2010
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
4862

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.

History

#1 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 4862

#2 Updated by ben leinfelder over 6 years ago

  • Assignee changed from Shaun Walbridge to ben leinfelder
  • Status changed from New to Closed

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.

Also available in: Atom PDF