Case insensitive attributeType names for bind and LDAPEntry

[twisted]

Case insensitive attributeType names for bind and LDAPEntry

[cwaldbieser]

I can confirm your observations. It is not entirely clear to me how the server should behave in this regard. I am assuming you are using the server from the quickstart example[1].

Even after reading the RFCs, I am not certain if this behavior is left up to the server or is govened by part of the specification.

[1] https://github.com/twisted/ldaptor/blob/master/docs/source/quickstart.rst

[adiroiban]

I am using the quickstart example. btw the quickstart example are awesome. great job. I was up and running in no time :)

---

I guess that all standard schemas, while they are defined with some of the letter in upper case ( ex businessCategory) there is no clash with another attribute defined somewhere else as BusinessCategory ... so I think that is safe to compare them in lowercase

I don't think that this is a serious bug/issues so I have just reported the observed behavior