[
https://issues.apache.org/jira/browse/DIRAPI-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18038516#comment-18038516
]
Emmanuel Lécharny commented on DIRAPI-427:
------------------------------------------
Hi GCHQDeveloper29 (sorry, I don't have your firstname),
can you at least share the kind of issue you have with the current code?
Because the only difference I can see regarding the result you get when doing a
search vs a lookup in this very case is that your server will return a wrong
entry because we don' use the {{(objectClass=subschema)}} filter. Is that the
case?
Thanks!
> 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]
