Handling M$ specification violations

2010-02-23 Thread Emmanuel Lecharny
Hi, M$, as usual, is violating many LDAP RFCs. For instance, you can send a simple BindRequest where the user name is *not* a DN. I guess we will have to bend the API to accept such crapity... wdyt ? M$ -- Regards, Cordialement, Emmanuel Lécharny www.nextury.com

Re: Handling M$ specification violations

2010-02-23 Thread Matthew Swift
I think so - I realize that our OpenDS SDK needs to cope with this as well :-( It makes me wonder what else could be violated? Should we permit non-DNs for all operations? E.g. modifying the entry "joe.blo...@example.com"? It seems a bit inconsistent to be lax in only one part of the protocol

Re: Handling M$ specification violations

2010-02-23 Thread Matthew Swift
I think so - I realize that our OpenDS SDK needs to cope with this as well :-( It makes me wonder what else could be violated? Should we permit non-DNs for all operations? E.g. modifying the entry "joe.blo...@example.com"? It seems a bit inconsistent to be lax in only one part of the protocol

Re: Handling M$ specification violations

2010-02-26 Thread Emmanuel Lecharny
On 2/23/10 10:06 PM, Matthew Swift wrote: I think so - I realize that our OpenDS SDK needs to cope with this as well :-( It makes me wonder what else could be violated? Should we permit non-DNs for all operations? IMO, no. E.g. modifying the entry "joe.blo...@example.com"? It seems a bit