Thanks,<br>I will solve my problem using ACL, forbidding access to that attribute using &quot;attrs=uid vals=pippo&quot; .<br><br>Marco<br><br><div class="gmail_quote">2010/9/20 Bjørn Ruberg <span dir="ltr">&lt;<a href="mailto:bjorn@ruberg.no">bjorn@ruberg.no</a>&gt;</span><br>

<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">On 09/20/2010 11:31 AM, Marco Pizzoli wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi list,<br>
I need to populate an entry in OL having DN uid=pippo,ou=people,dc=mycorp.<br>
<br>
I need to force this entry to have a uid attribute *different* from uid<br>
appearing in the name. Example: I need &quot;uid: pluto&quot;.<br>
ldapadd-ing the entry I have the entry with 2 uid attributes populated:<br>
- uid: pippo<br>
- uid: pluto<br>
<br>
Is there a way to NOT have &quot;uid: pippo&quot; populated even if the entry is<br>
called in that way?<br>
</blockquote>
<br></div>
No.<br>
<br>
The RDN (uid=pippo) *must* exist as a key:value attribute in the object.<br>
<br>
You can have both uid:pippo and uid:pluto in the object, but you will not be allowed to leave uid:pippo out.<br>
<br>
-- <br><font color="#888888">
Bjørn<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>_________________________________________<br>Non è forte chi non cade, ma chi cadendo ha la forza di rialzarsi.<br>                    Jim Morrison<br>