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

OpenDJ schema is broken #259

Closed
yurem opened this issue Jan 23, 2017 · 6 comments
Closed

OpenDJ schema is broken #259

yurem opened this issue Jan 23, 2017 · 6 comments
Assignees
Labels
bug issue in existing feature or functionality
Milestone

Comments

@yurem
Copy link
Contributor

yurem commented Jan 23, 2017

In latest OpenDJ shcema there are manay errors like this:

[23/Jan/2017:11:10:09 +0000] category=CORE severity=ERROR msgID=org.opends.messages.config.196 msg=An objectclass read from schema configuration file 100-user.ldif could not be parsed: The provided value "( 1.3.6.1.4.1.48710.1.4.1 name 'pairwiseidentifier' sup top structural must objectclasses: may ( oxid $ oxsectoridentifier ) x-origin 'gluu created objectclass' )" could not be parsed as an objectclass description because the non-numeric OID contained an illegal character : at position 89
@yurem yurem added the bug issue in existing feature or functionality label Jan 23, 2017
@yurem yurem added this to the CE 3.0.0 milestone Jan 23, 2017
yurem added a commit that referenced this issue Jan 23, 2017
yurem added a commit that referenced this issue Jan 23, 2017
@yurem
Copy link
Contributor Author

yurem commented Jan 23, 2017

I've fixed schema in setup. We also need to fix openldap->opendj schema migrator. In it's code there is bug which add ":" after the objectClass in wrong places.

yurem added a commit that referenced this issue Jan 23, 2017
@yurem
Copy link
Contributor Author

yurem commented Jan 23, 2017

Also converter produces:

...MUST objectClasses... and ...MUST ( objectClasses )... 

But right value should be:

...MUST objectClass...

@tecoholic
Copy link
Contributor

The convertor is not the code written by us. It is taken from https://github.com/ludomp/opendj-utils/blob/master/schema-convert.py. It is licensed under some CDDL license, I think we should be better off by writing a new convertor. Schema management is something on the TODO list, so this convertor should be available sometime in the future.

@yurem yurem modified the milestones: CE 3.1.0, CE 3.0.0 Jan 27, 2017
@yurem
Copy link
Contributor Author

yurem commented Jan 27, 2017

ok, changing milestone...

@tecoholic
Copy link
Contributor

I have begun working on it. This can be done by 3.0 release.

@tecoholic
Copy link
Contributor

This has been fixed with the new schema management suite of scripts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug issue in existing feature or functionality
Projects
None yet
Development

No branches or pull requests

2 participants