Am 01.03.21 um 10:37 schrieb Rowland Penny:
On 01/03/2021 06:40, Roland Gruber wrote:
Hi Rowland,
sorry, there is still a misunderstanding. I was referring to an
operation on Samba side as below. It is about adding the object class
and attribute on an existing user. This fails while adding both in two
steps is ok.
This is with version 4.9.5. Not sure if you know if that was fixed in
current Samba release?
[2021/02/28 21:02:29.480794, 10, pid=1601, effective(0, 0), real(0,
0), class=ldb] ../lib/ldb-samba/ldb_wrap.c:79(ldb_wrap_debug)
ldb: ldb_trace_request: MODIFY
dn: cn=aaaa \2Caaaaa,DC=samba4,DC=test
changetype: modify
add: objectClass
objectClass: ldapPublicKey
-
add: sshPublicKey
sshPublicKey: 123
-
No, you don't 'add' them, you just 'modify' them, this ldif works:
dn: CN=aaaaaa bbbbb,CN=Users,DC=samdom,DC=example,DC=com
changetype: modify
objectClass: ldapPublicKey
sshPublicKey:
MIIEpAIBAAKCAQEAuzcrOUvKaWA7aDdbB5e2GnHTP1EVUI0l8RRNwd87rrILV9Q3
The issue is also on Samba 4.13.4 and can be reproduced with local
ldapmodify command. But it seems to be related to the object class /
attribute definition.
The same type of operation to add e.g. shadow account works without any
issues:
changetype: modify
add: objectClass
objectClass: shadowAccount
-
add: shadowWarning
shadowWarning: 123
-
@Rowland: do you see any issues in the schema definition provided by
Joshua? I never saw this error on other schema extensions.
Best regards
Roland
_______________________________________________
Lam-public mailing list
Lam-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lam-public