[
https://issues.apache.org/jira/browse/DIRSTUDIO-563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764740#action_12764740
]
Emmanuel Lecharny commented on DIRSTUDIO-563:
---------------------------------------------
I think the best would be to use the new Shcema manager we are working on in
the server. It will allow way more options.
> Evaluate removal of default schema
> ----------------------------------
>
> Key: DIRSTUDIO-563
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-563
> Project: Directory Studio
> Issue Type: Task
> Components: studio-ldapbrowser
> Affects Versions: 1.4.0, 1.5.0
> Reporter: Stefan Seelmann
> Fix For: 2.0.0
>
>
> Studio contains a built-in schema that is derived from OpenLDAP and contains
> all standard schema objects. It is used in case that a schema can't be read
> from a connected LDAP server (i.e. if it is hidden by ACL).
> If the server only uses standard schema objects this approach works fine.
> However when custom schema objects are used Studio can't guess which
> attributes are allowed or required and pops up wrong warnings.
> We should evaluate if it would better to remove the default schema and to
> disable schema checks if no schema is present.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
