Hello,
Also as a general rule the X.500 data model requires that a server
store and return exactly what the user provided.
please tell me where in X.500 you find this. I couldn't find it.
Instead I found (X.501 (2008), chapter 13.3.2 ( The object class
attribute) :
Every entry shall
Keutel, Jochen (mlists) wrote:
Hello,
Also as a general rule the X.500 data model requires that a server store
and return exactly what the user provided.
please tell me where in X.500 you find this. I couldn't find it. Instead I
found (X.501 (2008), chapter 13.3.2 ( The object class
Hello,
if I add an entry like this:
dn: cn=jk,dc=test
objectClass: inetOrgPerson
cn: jk
sn: jk
This works fine. Esp. the superclasses seem to be added on the fly:
Searching this entry with filter objectClass=person works fine.
However - when I read this entry I'd expect that all
Am 22.03.2013 um 14:06 schrieb Keutel, Jochen (mlists) mli...@keutel.de:
Hello,
if I add an entry like this:
dn: cn=jk,dc=test
objectClass: inetOrgPerson
cn: jk
sn: jk
This works fine. Esp. the superclasses seem to be added on the fly:
Searching this entry with filter
Manuel Gaupp wrote:
I don't think so, because RFC 4512, section 3.3 says:
When creating an entry or adding an 'objectClass' value to an entry,
all superclasses of the named classes SHALL be implicitly added as
well if not already present. [...]
If I'm interpreting this correctly,
Michael Ströder wrote:
Manuel Gaupp wrote:
I don't think so, because RFC 4512, section 3.3 says:
When creating an entry or adding an 'objectClass' value to an entry,
all superclasses of the named classes SHALL be implicitly added as
well if not already present. [...]
If I'm
