summaryrefslogtreecommitdiff
path: root/source4/dsdb/samdb/ldb_modules/operational.c
AgeCommit message (Collapse)AuthorFilesLines
2009-12-03s4:operational LDB module - Fix usage of LDB constantsMatthias Dieter Wallnöfer1-4/+4
2009-11-26s4:operational LDB module - Don't do the write checks hereMatthias Dieter Wallnöfer1-16/+0
Let this perform the schema in the "objectclass" module.
2009-11-24s4:operational LDB module - Prevent the modification of operational attributesAndrew Bartlett1-0/+16
(merged by Andrew Bartlett) Signed-off-by: Andrew Bartlett <abartlet@samba.org>
2009-11-24s4:dsdb Return the subSchemaSubEntry operational attribute on every objectAndrew Bartlett1-4/+40
2009-11-20Cosmetic patch - fixed case of attribute name.Nadezhda Ivanova1-1/+1
2009-11-20s4-dsdb: some more attribuutes that we should only give if asked forAndrew Tridgell1-1/+6
2009-11-20s4-dsdb: removed attributes that should not be displayed by defaultAndrew Tridgell1-0/+37
Some attributes (like ntSecurityDescriptor) are stored in our db, but should only be displayed if asked for. This also applied to parentGUID from old installs, which is now generated.
2009-11-20s4-drs: Synchronous Implementation of generated parentGUIDFernando J V da Silva1-2/+34
This generated parentGUID on demand, rather than getting it from the database Signed-off-by: Andrew Tridgell <tridge@samba.org>
2009-09-12s4-samdb: internal s4 ldb modules should be GPL not LGPLAndrew Tridgell1-15/+11
I think these modules ended up LGPL because someone based the module on an existing LGPL module in the core ldb, and it spread from there. Certainly there is no reason for the ldb modules that are not distributed as part of ldb to be LGPL.
2009-08-11s4:operational - Remove some outdated commentsMatthias Dieter Wallnöfer1-12/+0
2009-08-11s4:operational module - move and enhancementsMatthias Dieter Wallnöfer1-0/+347
This moves the "operational" LDB module to the right place under "dsdb/samdb/ldb_modules" (suggested by abartlet) and enhances it for supporting dynamic generated "primaryGroupToken" for AD groups. This should fix bug #6466.