AFP548

3rd Party LDAP and Group Membership

We have integrated OS X and Novell's eDirectory for many years. We have extended the schema so we are storing our apple-attributes directly in eDirectory. This has worked well for us and allowed us to manage our clients with Workgroup Manager with ease. We have not stored an apple-generateduid attribute for our users before, because they just weren't necessary. Starting in Leopard, we started having a few weird issues. When we would add a user to a group, Workgroup Manager would do it's thing where it autocreated a generateduid (UUID) similar to what is referenced in this post . Because it was not a "real" UUID (which gets stored in the GroupMembers attribute), we would have problems deleting a user from a group, because it wouldn't delete the corresponding GroupMembers value. So, I used uuidgen to generate UUIDs and populate the apple-generateduid field for all the users. No problem there. When I went to add a list of students to a group, though, the group "Members" tab showed the complete list of UUID numbers in the ID section (instead of the UID), with the "Name" section showing "Not Found". The entire list of students was 521 users. What I discovered was that I could successfully add 490 to 495 users to the group successfully (depending on the list of users being added), and Name, ID, Type, and Short Name fields would all show exactly the right data, but once I exceeded that number, it all went back to displaying UUIDs and Not Found. Am I exceeding the capacity of the apple-group-memberguid field in eDirectory? That's what it feels like to me. Is the problem something else? Thanks for any input.
Exit mobile version