On 26 July 2013 00:12, Quanah Gibson-Mount <qua...@zimbra.com> wrote:
> For a stock openldap install, any attribute that is hard coded in > ppolicy.c is available once the module is loaded. Whether or not one also > requires the ppolicy.[schema|ldif] file depends entirely on whether or not > they also need access to those attributes defined within them. If all you > need are the hard-coded attributes, then you can skip loading the > additional schema file. > Ok, so it looks like the ppolicy module only adds certain attributes. ppolicy.ldif is still required to load the objectClass required for ppolicy. I assume that there must be a good reason for splitting the ppolicy schema up between the schema file and the module like this. Anyway, I may not be the bug submitter, however I think this bug can be closed. The attributes are there, just in the module not the schema file. -- Brian May <br...@microcomaustralia.com.au>
