[
https://issues.apache.org/jira/browse/DIRAPI-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18038289#comment-18038289
]
Emmanuel Lécharny commented on DIRAPI-427:
------------------------------------------
Regarding the issue:
- the reason we do a lookup instead of a search with an
{{(objectclass=subschema)}} filter is that most of the LDAP servers I know of
are supporting one single schema for the whole LDAP server, which is a
{{rootDSE}} subentry.
- Actually, doing a search with scope = {{OBJECT}} on the {{rootDSE}} entry is
exactly equivalent as doing a lookup on the subentry itself.
So I believe the change you are suggesting has no effect in the result it
returns.
Do you have example of potential issues with some specific LDAP servers with
which the lookup request does not work properly?
Many 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]
