Ah, sorry for my bad, it's actually there. From the wiki link, it looks much fine for kerby-asn1 to handle if we'd like the approach. Will have some time to experiment. Thanks.
Regards, Kai -----Original Message----- From: Emmanuel Lécharny [mailto:[email protected]] Sent: Friday, December 18, 2015 6:53 PM To: Apache Directory Developers List <[email protected]> Subject: Re: [VOTE] Apache LDAP API 1.0.0-M33 release Le 18/12/15 11:14, Zheng, Kai a écrit : > Thanks for the details. The encoding rules are actually much simplified and > kerby-asn1 would be sure to be able to parse. The problem is I didn't find > clear ASN1 definitions as we found for Kerberos, PKINIT, CMS and X509. What's > kerby-asn1 is good at is, starting with a ASN1 defined type, the Java > pojo/model class can be easily written and the class can be inherently of > encoding/decoding capabilities and can also be clearly dumped out. Below is > an example we did recently for CMS. It follows BER encoding, using > indefinitive length. Without clear ASN1 type definitions, kerby-asn1 would > not be much more helpful than other ASN1 library supports I'm afraid. The RFC 4511 defines the full ASN.1 grammar for LDAP (at teh end). You can also have a look at https://cwiki.apache.org/confluence/display/DIRxSRVx10/Ldap+ASN.1+Codec
