Empty attributes from AD are missing

[richardun]

In my active_directory gem, I use net-ldap. I have accounts that have empty attributes in AD, like extensionattribute2. When I pull the entry through my gem and look for that attribute, it's not there. However, if I add something to it in AD and do another search, the entry now has the attribute.

I need to be able to write values to attributes that will be empty from AD. Would you be so kind as to help me figure out where I'm going wrong? Essentially, I'm getting a "no id given" ArgumentError.

I'm asking you because I think that net-ldap is not returning attributes that are empty. Perhaps there is some property-add function I can write in my own clone of ruby-net-ldap, but I would need some guidance to see if I'm anywhere near being correct.

Thanks in advance,
Richard

[mtodd]

Hi @richardun, Net::LDAP::Entry objects are not schema-aware and if an entry is sent over the wire without an attribute set, Net::LDAP won't know to create it.

I'd be curious to see what API you're using to set values where you get that error. You should be able to set an attribute value on a Net::LDAP::Entry object with entry[:extensionattribute2] = "foo". But that won't add the attribute to the entry on the server side, you need to use ldap.add_attribute to do that.

Going to close this, though, since it doesn't sound like it's a specific issue with the client library. Let me know if I've missed an important detail!