Apart from the OID, I wouldn't make the ownCloudAccount a structural objectclass. The LDAP accounts belong to existing users. So it would be better to use an auxiliary objectclass that only needs the ownCloudQuota attribute:

objectclass ( 1.1.2.2.10
      NAME 'ownCloudAccount'
      DESC 'ownCloud LDAP Schema'
      SUP top
      AUXILIARY
      MAY ( ownCloudQuota )
   )

And I don't see why you need an own group. In the LDAP configuration of owncloud you can choose, if you want to use a posixGroup, a groupOfNames or a groupOfUniqueNames.


objectclass ( 1.1.2.2.10
     NAME 'ownCloudAccount'
     DESC 'ownCloud LDAP Schema'
     SUP top
     STRUCTURAL
     MUST ( uid $ userPassword )
     MAY ( displayName $ ownCloudQuota $ email $ cn )
  )

objectclass ( 1.1.2.2.11
     NAME 'ownCloudGroup'
     DESC 'ownCloud Group'
     SUP top
     STRUCTURAL
     MUST ( cn $ displayName )
     MAY uniqueMember
  )


Attachment: smime.p7s
Description: S/MIME Kryptografische Unterschrift

_______________________________________________
Owncloud mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/owncloud

Reply via email to