directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (DIRAPI-244) Error in loading schema
Date Fri, 14 Aug 2015 06:41:45 GMT

    [ https://issues.apache.org/jira/browse/DIRAPI-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14696571#comment-14696571
] 

Emmanuel Lecharny edited comment on DIRAPI-244 at 8/14/15 6:40 AM:
-------------------------------------------------------------------

You are most certainly trying to load an AD schema. As usual, Microsoft made all it can to
twist the RFC and make it almost impossible for tools that actually try to follow the specifications
to work.

In this very case, the AttributeType specification, as exposed in {{RFC 4512}}, makes the
{{USAGE}} keyword mandatory when the {{NO-USER-MODIFICATION}} is present:

{code}
   NO-USER-MODIFICATION requires an operational usage.
{code}

This make a lot of sense, because there are three kind of operational usage, and we must know
which one of the three to use. 

Bottom line, I would ask you : why are you using AD, which is just a piece of crap ? Not only
it does not implements the LDAP RFCs correctly (knowing Microsoft, mostly on purpose), but
it's also an inferior so-called LDAP implementation, when it comes to reliability and performance
(and it's a matter of orders of magnitude in this case).

Ok, rant put aside, here, I have no quick solution. We *should* and we *would* get the API
to swallow the crippled Microsoft schema in the near future (and we actually working on making
the API to do that), but it will take a bit of time.

Technically speaking, we can allow an AttributeType to have the {{NO-USER-MODIFICATION}} specifier
without an {{USAGE}}, making the attributeType an operational attributeType (most certainly
a {{directoryOperation}}, but I'm not sure, seems like the systemFlags AT is used for replication,
and that would dive us to pick another usage. Assuming M$ accept any of those three Operational
Usage). 

FTR, here is the Microsoft broken definition of an {{Operational Attribute}} : https://technet.microsoft.com/en-us/library/ee156512.aspx

It's not even remotely close to any LDAP RFC. At all.



was (Author: elecharny):
You are most certainly trying to load an AD schema. As usual, Microsoft made all it can to
twist the RFC and make it almost impossible for tools that actually try to follow the specifications
to work.

In this very case, the AttributeType specification, as exposed in {{RFC 4512}}, makes the
{{USAGE}} keyword mandatory when the {{NO-USER-MODIFICATION}} is present:

{code}
   NO-USER-MODIFICATION requires an operational usage.
{code}

This make a lot of sense, because there are three kind of operational usage. 

Bottom line, I would ask you : why are you using AD, which is just a piece of crap ? Not only
it does not implements the LDAP RFCs correctly (knowing Microsoft, mostly on purpose), but
it's also an inferior so-called LDAP implementation, when it comes to reliability and performance
(and t's a matter of orders of magnitude in this case).

Ok, rant put aside, her, I have no quick solution. We *should$ and we *would* get the API
to swallow the crippled Microsoft schema in the near future (and we actually working on making
the API to do that), but it will take a bit of time.

Technically speaking, we can allow an AttributeType to have the {{NO-USER-MODIFICATION}} specifier
without an {{USAGE}}, making teh attributeType an operational attributeType (most certainly
a {{directoryOperation}}, but I'm not sure). 

FTR, here is the Microsoft broken definition of an {{Operational Attribute}} : https://technet.microsoft.com/en-us/library/ee156512.aspx

It's not even remotely close to any LDAP RFC. At all.


> Error in loading schema
> -----------------------
>
>                 Key: DIRAPI-244
>                 URL: https://issues.apache.org/jira/browse/DIRAPI-244
>             Project: Directory Client API
>          Issue Type: Bug
>    Affects Versions: 1.0.0-M31
>            Reporter: Steven Nguyen
>
> Hi Team,
> I have an issue in loading schema in LDAPNetworkConnection.
> I could connect to my Active Directory host, however when I call the loadSchema() method,
it threw out below exception
> java.text.ParseException: ERR_04228 Parser failure on attribute type description: ( 1.2.840.113556.1.4.375
NAME 'systemFlags' SYNTAX '1.3.6.1.4.1.1466.115.121.1.27' SINGLE-VALUE NO-USER-MODIFICATION
) Antlr message: NO-USER-MODIFICATION requires an operational USAGE Antlr column: 0: ERR_04228
Parser failure on attribute type description: ( 1.2.840.113556.1.4.375 NAME 'systemFlags'
SYNTAX '1.3.6.1.4.1.1466.115.121.1.27' SINGLE-VALUE NO-USER-MODIFICATION ) Antlr message:
NO-USER-MODIFICATION requires an operational USAGE Antlr column: 0: NO-USER-MODIFICATION requires
an operational USAGE
> Could you please advise?
> Best Regards,
> Steven Nguyen



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message