[Date Prev][Date Next]
Re: (ITS#4947) monitor schema should appear under subschema entry
--On Friday, May 04, 2007 2:39 PM +0000 email@example.com wrote:
> Full_Name: Andreas Hasenack
> Version: 2.3.35
> OS: Linux
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (22.214.171.124)
> (enhancement, or minor)
> The monitor backend attributes and object classes, when loaded, should
> also be exported in the subschema entries at the server.
> I know of one ldap client that breaks because of this: luma. It says it
> can't display the cn=monitor entries because it doesn't know the object
> classes or attributes. I guess it uses this info to determine how to show
> each entry.
Not disagreeing, but making the assumption that cn=subschema is readable is
also a broken behavior on the luma side.
Principal Software Engineer
Zimbra :: the leader in open source messaging and collaboration