[
https://issues.apache.org/jira/browse/DIRAPI-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18038517#comment-18038517
]
Emmanuel Lécharny commented on DIRAPI-427:
------------------------------------------
Also note, for completion, that I have no problem with your PR, it will do the
job, adding an extra check on the ObjectClass.
What I don't get is why your server fails with the lookup. The only possibility
being that the lookup returns an entry that does not please the remaining
code, while you don't get anything with the search because of the filter. Which
means the subschemaSubentry does not contains the {{subschema}} objectClass...
> Update DefaultSchemaLoader to comply with RFC-4512 section 4.4 'Subschema
> Discovery'
> ------------------------------------------------------------------------------------
>
> Key: DIRAPI-427
> URL: https://issues.apache.org/jira/browse/DIRAPI-427
> Project: Directory Client API
> Issue Type: Improvement
> Affects Versions: 2.1.7
> Reporter: gchqdeveloper29
> Priority: Trivial
> Fix For: 2.1.8
>
>
> Currently the DefaultSchemaLoader doesn't function for all directory server
> software as it does not use the '(objectClass=subschema)' filter when
> querying the subschemaSubentry, but instead a direct lookup.
> This causes the DefaultSchemaLoader to not function for other pieces of
> directory software.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
