[
https://issues.apache.org/jira/browse/DIRAPI-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18038330#comment-18038330
]
gchqdeveloper29 commented on DIRAPI-427:
----------------------------------------
Hi Emmanuel,
I do have an example with a specific piece of directory software, that the
current method of retrieving the schema does not work with.
I have tested my code changes against it, and it now does work. (The software
was built to be schema compliant).
Unfortunately, I'm not at liberty to say which software is being used.
Kind Regards,
GCHQDeveloper29
> 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]
