[
https://issues.apache.org/jira/browse/DIRAPI-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18038897#comment-18038897
]
gchqdeveloper29 commented on DIRAPI-427:
----------------------------------------
Hi Emmanuel,
The server cannot even find the entry without the object class filter.
It is something I have raised with the vendor, but figured there may be other
software in a similar state, so raised it as a PR to fix forward for other use
cases (along with this).
> 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]
