Michael Str�der wrote: > Rich Megginson wrote: > >> Michael Str�der wrote: >> >>> Rich Megginson wrote: >>> >>>> >>>> It may "know" about operational attributes, either by hard coding >>>> them or by reading the schema. >>> >>> >>> Hmm, for determining all available attributes by looking at sub >>> schema sub entry one has to know all object classes of an entry. >>> [..] >>> But some are hidden too (e.g. passwordObject). >> >> [..] >> Is passwordObject an objectclass? > > > Yes. > >> And it is not listed in the schema? > > > It is correctly listed in the sub schema sub entry but not in the > attribute value list of attribute objectClass.
Sounds like a bug . . . > However the attributes required/allowed in this particular object > class passwordObject are in the entry and readable (by explicitly > requesting them). Weird. Kind of like an "operational objectclass". > => It's not possible in general to determine the available operational > attributes by looking at the schema - at least with iPlanet DS 5.1. > Not sure about others. With iDS 5.1 and Netscape DS 6.0 it is possible to determine all operational attributes - they are denoted as operational in the cn=schema entry. However, it is not possible to determine which of those should be present in particular entries. In general, all of them are present in every entry, but there are a couple of exceptions. > > > Ciao, Michael. >
