Have you tried âhackingâ your schema, and change for example âSTRUCTURALâ to âAUXILIARYâ. In that case you would be able to specify both posixGroup and groupOfMembers, or even use groupOfNames.
Have a lok at this
I am also struggling to understand what is the best way to implement this, and I would really appreciate if somebody already done it, and can share the idea.
So, what is the right way? Could you give me an example how to set this up or give me a reference to a good source on this?
2012/2/22 Howard Chu <email@example.com>
Fred van Zwieten wrote:
I fail to see how this solves my RBAC need.
Let me give an example:
Say, personA is in ou DeptA. Then, ideally personA would based on being in
this ou, become member of group webserver
No, when I move personA to ou DeptB, this would mean that, on the next login,
it looses it's membership to group Webserver, but now becomes member of ie
This way, you implement security policies based on the role of a person.
This is not the right way to implement roles. Generally DNs are intended to be constant (though obviously they are allowed to change, changes should be infrequent).
How could this ideally be done with OpenLDAP?
Â Â Â Âpersons should use inetOrgPerson and PosixAccount schemas : gidNumber
Â Âgives primary group.
Â ÂThen define specific branch ou=posix based on PosixGroup schema and add
Â Âthe uid of the person in memberUid multiple values attribute to specify
Â Âsecondary gid.
Â ÂLe 22/02/2012 10:22, Fred van Zwieten a Ãcrit :
Â ÂHi all,
Â Âwarning: openldap newbie..
Â Âis it possible to have a person put into an OU and, because of this,
Â Âwill become member of some group in such a way that this group shows up
Â Âin linux using "id". This to implement some form of RBAC. I found
Â ÂGroupofMembers, but that has nothing to do with OU's. Also, it seems
Â ÂposixGroup and groupOfMembers objecttypes are no longer allowed together
Â Âbecause the are both STRUCTURAL.
Â ÂIn AD this is possible.
Â ÂFred <http://epsilon.eridani.nl>