RE: 2 issues with Password policy response warnings / types

2012-06-22 Thread Carlo.Accorsi
OK, Thank you very much for the clarification. I really thought I had it right. Last question on this. In the case where the length after the 0x80 is 1. As below, where the length is 2. 30, 9, a0, 4, 80, 2, 0, d0, 81, 1, 2, Do you know how to decode the int value? I'm looking for 208,

Re: 2 issues with Password policy response warnings / types

2012-06-22 Thread Kiran Ayyagari
take a look at the class org.apache.directory.shared.asn1.ber.tlv.IntegerDecoder On Sat, Jun 23, 2012 at 12:39 AM, carlo.acco...@ibs-ag.com wrote: OK, Thank you very much for the clarification.  I really thought I had it right. Last question on this.  In the case where the length after the

RE: 2 issues with Password policy response warnings / types

2012-06-22 Thread Carlo.Accorsi
Thanks that's great! Carlo Accorsi -Original Message- From: ayyagariki...@gmail.com [mailto:ayyagariki...@gmail.com] On Behalf Of Kiran Ayyagari Sent: Friday, June 22, 2012 3:15 PM To: users@directory.apache.org Subject: Re: 2 issues with Password policy response warnings / types

Re: 2 issues with Password policy response warnings / types

2012-06-22 Thread Emmanuel Lécharny
Le 6/22/12 10:54 PM, carlo.acco...@ibs-ag.com a écrit : Thanks that's great! There is also a class that handle all the decoding and creates a plain Java object with all the expected data : DefaultLdapCodecService codec = new DefaultLdapCodecService();

Re: 2 issues with Password policy response warnings / types

2012-06-22 Thread Emmanuel Lécharny
Le 6/22/12 9:09 PM, carlo.acco...@ibs-ag.com a écrit : OK, Thank you very much for the clarification. I really thought I had it right. Last question on this. In the case where the length after the 0x80 is 1. As below, where the length is 2. 30, 9, a0, 4, 80, 2, 0, d0, 81, 1, 2, Do you know