Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[#425] Add option -Dorg.openidentityplatform.opendj.ERR_ENTRY_SCHEMA_VIOLATES_PARENT_DSR for force control "Entry is invalid according to the server schema because there is no DIT structure rule that applies to that entry, but there is a DIT structure rule for the parent entry". Default: warning level #435

Merged
merged 4 commits into from
Oct 17, 2024

Conversation

vharseko
Copy link
Member

Closes #425

…s invalid according to the server schema because there is no DIT structure rule that applies to that entry, but there is a DIT structure rule for the parent entry
@JesseCoretta
Copy link
Contributor

Following a cursory review of the code, given my limited Java skills, this looks to be effective and efficient.

Because this is fixed now, I will update #422 again to state that the issue is fixed now, but earlier versions of OpenDJ would require the name form described in my I-D (derived from ITU-T Rec. X.501 clause 14.2.2) to circumvent this error.

Agreed @vharseko / @maximthomas ?

…dj.ERR_ENTRY_SCHEMA_VIOLATES_PARENT_DSR for force control "Entry is invalid according to the server schema because there is no DIT structure rule that applies to that entry, but there is a DIT structure rule for the parent entry". Default: warning level
@vharseko vharseko changed the title [#425] FIX exclude subentry OC violation: Entry is invalid according to the server schema because there is no DIT structure rule that applies to that entry, but there is a DIT structure rule for the parent entry [#425] Add option -Dorg.openidentityplatform.opendj.ERR_ENTRY_SCHEMA_VIOLATES_PARENT_DSR for force control "Entry is invalid according to the server schema because there is no DIT structure rule that applies to that entry, but there is a DIT structure rule for the parent entry". Default: warning level Oct 17, 2024
@vharseko vharseko merged commit 23e84fb into OpenIdentityPlatform:master Oct 17, 2024
17 checks passed
@vharseko vharseko deleted the issue/425 branch October 17, 2024 12:25
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@maximthomas / @vharseko

I think this push was incomplete -- we were supposed to include the name form definition not only in our test, but in our schema library.

I have just installed the newest build you released, and the name form is nowhere to be found in the included collection of definitions.

Furthermore, because we expected it to be present, this is why I phrased the document updates as follows:

As such, the OpenDJ package conveniently includes the equivalent LDAP name form definition
within the subschema subentry for users to leverage:

nameForms: ( 2.5.15.16
   NAME 'subentryNameForm'
   DESC 'X.501, cl. 14.2.2: the Subentry name form'
   OC subentry
   MUST cn )

Because the name form is present in your test, but not in our /schema directory, this will result in errors needlessly.

Please explain.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Log info:

[17/Oct/2024:19:34:53 -0700] category=CONFIG severity=WARNING msgID=761 msg=The config
schema file '99-custom.ldif' generated warning when trying to update schema with its content:
[Validation of DIT structure rule definition ( 50 NAME 'subentryStructure' FORM subentryNameForm
SUP ( 30 31 ) X-SCHEMA-FILE '99-custom.ldif' ) failed and will be removed from the schema: 
The provided value "subentryStructure" could not be parsed as a DIT  structure rule description
because it referenced an unknown name form subentryNameForm]

The relevant message component is:

... because it referenced an unknown name form subentryNameForm

Command I used to check schema collection:

jesse@localhost /opt/opendj/config/schema$ grep '2.5.15.16' *
<no results>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants