Yes. Re-read the rdoc. The DN which specifies the entry to which you are
adding the attribute is the first parameter.
i think i’m using it properly.
ldap.add_attribute gr, :member, $dnwks
“gr” is the group to which i want to add an entry.
“:member” is the attribute.So i will add the member $dnwks to gr.
“$dnwks” is the object i want to add.
also it tried various combination but it get worst.
Ah. Sounds like the problem was a schema violation all along, then. That
also is consistent with a 53 error code.
yes it was.thx.
I had 2 other questions the first one is related to this post (no subject) - Ruby - Ruby-Forum and i was wondering if
other people asked for it and if so ;do you think it might be supported?
if not what would be a good work around ?
#add_attribute and #modify are essentially the same protocol on the
wire. I
doubt the client-side code for one is much faster than the other. If it
were, the network latency would probably be far more than the difference
anyway.
I had 2 other questions the first one is related to this post (no subject) - Ruby - Ruby-Forum and i was wondering if
other people asked for it and if so ;do you think it might be supported?
if not what would be a good work around ?
and i forgot my 2nd question.would ldap.modify be faster than
ldap.add_attribute ?
I had 2 other questions the first one is related to this post (no subject) - Ruby - Ruby-Forum and i was wondering if
other people asked for it and if so ;do you think it might be supported?
if not what would be a good work around ?
I have to confess that I 'm still not clear on what you want to do in
regard
to the password storage problem. Net::LDAP already has the ability to
take a
Ruby block in place of a String password in the places where a password
is
required (Net::LDAP#open, Net::LDAP#new). Check that out and see if you
can
use it. If not, then I’ll need a more clearly-stated feature request.
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.