Hi everyone,<br><br>I just installed 389-ds on Fedora and have a problem with Solaris clients.<br><br>Everything works well on the Linux side (Fedora, CentOS and RHEL clients works fine).<br><br>On the Solaris side, I got everything to work too (pam, ssh, getent passwd, getent group, ldaplist -l paswd, ldaplist -l group, etc). I used the native Solaris ldapclient tool to make everything work.<br>
<br>The problem I have is with the Group attribute. In 389-ds, the group are created with the objectClass &quot;groupofuniquenames&quot; and the members are listed with the attribute &quot;uniqueMember&quot;. I manually add the objectClass &quot;posixgroup&quot; to allow the group to be visible on the client.<br>
<br>With this configuration, everything work fine in Linux. In Solaris, I can see the group with &quot;getent group&quot; but there are no member. What I have found is that Solaris need it&#39;s member to be in the &quot;memberUid&quot; attribute and not in the &quot;uniqueMember&quot; attribute.<br>
<br>Also, I found that while uniqueMember require a full qualification (uid=jeff,ou=people,dc=test,dc=com), the memberUid just require the uid (jeff).<br><br clear="all"><br>What should I do to make this work easy on Solaris? Adding the memberUid by hand is not an option because it&#39;s sure there will be a difference between the uniqueMember and memberUid list in some point in time.<br>
<br><br>Thank you!<br><br>-- <br>Jean-Francois Saucier (djf_jeff)<br>GPG key : 0xA9E6E953<br>