summaryrefslogtreecommitdiff
path: root/source4/dsdb/samdb/ldb_modules/proxy.c
diff options
context:
space:
mode:
authorMatthias Dieter Wallnöfer <mdw@samba.org>2010-11-03 18:02:28 +0100
committerMatthias Dieter Wallnöfer <mdw@samba.org>2010-11-03 17:48:18 +0000
commit53d9d4ee0e6ee889a06c2d1134ddb083be45f91a (patch)
treeb6f5f48c8ec2d55b04b2c9addfa377e415372b95 /source4/dsdb/samdb/ldb_modules/proxy.c
parentb78bf4d72100f9aa8c50ee36b30ba353e2b72eae (diff)
downloadsamba-53d9d4ee0e6ee889a06c2d1134ddb083be45f91a.tar.gz
samba-53d9d4ee0e6ee889a06c2d1134ddb083be45f91a.tar.bz2
samba-53d9d4ee0e6ee889a06c2d1134ddb083be45f91a.zip
s4:sam.py - assign valid values when performing the special-attributes constraint checks
The problem is that s4 per construction does the checks in a different order. It first checks for validity (pre-operation trigger in samldb LDB module) and then for the schema (post-operation trigger in objectclass_attrs LDB module). constraints (post-operation trigger
Diffstat (limited to 'source4/dsdb/samdb/ldb_modules/proxy.c')
0 files changed, 0 insertions, 0 deletions