Membership types

Membership types are the possible roles that can be assigned to users in groups.




<field name="membershipTypeURL">

  <string>ou=memberships,ou=portal,dc=exoplatform,dc=org</string>

</field>

<field name="membershipTypeLDAPClasses">

  <string>top,organizationalRole</string>

</field>

<field name="membershipTypeNameAttr">

  <string>cn</string>

</field>

membershipTypeURL: base dn for membership types storage.

eXo stores membership types in a flat structure under membershipTypeURL. For example, roles, including manager, user, admin and editor could be defined by the subtree:

           
ou=roles,ou=portal,dc=exoplatform,dc=org
...
  cn=manager,ou=roles,ou=portal,dc=exoplatform,dc=org
  ...
  cn=user,ou=roles,ou=portal,dc=exoplatform,dc=org
  ...
  cn=admin,ou=roles,ou=portal,dc=exoplatform,dc=org               
  ...
  cn=editor,ou=roles,ou=portal,dc=exoplatform,dc=org
  ...

membershipTypeLDAPClasses: commas are used to separate list of classes for creating membership types.

When a new membership type is created, an entry will be also created with the given objectClass attributes. The classes must define the required attributes: description, cn.

For example, adding the membership type validator would produce:

          
cn=validator,ou=roles,ou=portal,dc=exoplatform,dc=org
  objectclass: top
  objectClass: organizationalRole
  ...

membershipTypeNameAttr: Attribute will be used as the name of the role.

For example, if membershipTypeNameAttr is cn, the role name will be manager for the following membership type entry:

cn=manager,ou=roles,ou=portal,dc=exoplatform,dc=org