summaryrefslogtreecommitdiff
path: root/source4/dsdb/samdb/ldb_modules/instancetype.c
AgeCommit message (Collapse)AuthorFilesLines
2012-07-18s4-dsdb: Allow dbcheck to correct an incorrect instanceTypeAndrew Bartlett1-3/+5
2011-10-04s4-dsdb: allow uninstantiated NC headsAndrew Tridgell1-2/+4
this allows INSTANCE_TYPE_WRITE to be not set if INSTANCE_TYPE_UNINSTANT is set
2011-03-10s4:instancetype LDB module - perform here only the "instanceType" constraint ↵Matthias Dieter Wallnöfer1-78/+16
checks The boilerplate entries (when this support has been implemented) should be provided by the "new_partition" LDB module. These are for example the deleted object and lost and found container.
2011-03-10s4:instancetype LDB module - don't impede control requestsMatthias Dieter Wallnöfer1-0/+7
2011-03-10s4:instancetype LDB module - use "ldb" pointer for referencing the LDB contextMatthias Dieter Wallnöfer1-1/+1
2010-11-01s4-ldb: enable version checking in dsdb ldb modulesAndrew Tridgell1-0/+1
2010-11-01s4-dsdb: convert the rest of the ldb modules to the new module typeAndrew Tridgell1-1/+6
2010-10-16s4:dsdb - fix unsigned integer save problems using the "%u" specifierMatthias Dieter Wallnöfer1-1/+1
The issue here is that we have not yet first cast to int32_t explicitly, before we cast to an signed int to printf() into the %d or cast to a int64_t before we then cast to a long long to printf into a %lld. There are *no* unsigned integers in Active Directory LDAP, even the RID allocations and ms-DS-Secondary-KrbTgt-Number are *signed* quantities. (See the schema, and the syntax definitions in schema_syntax.c). The failure has been detected by Matthieu Patou on the buildfarm host "tridge" due to a malformed "groupType" attribute. The solution is to use the "%d" specifier. Either to use it directly - or better (when possible) use the call "samdb_msg_add_uint" (which encapsulates it). This patch changes such problematic situations.
2010-09-25ldb: mark the location of a lot more ldb requestsAndrew Tridgell1-1/+2
2010-08-01s4:instancetype LDB module - add checks requested by MS-ADTS 3.1.1.5.2.2Matthias Dieter Wallnöfer1-6/+20
We've to test for the WRITE flag if we are performing an NC add. And if it isn't an NC add then only the WRITE or no flag is allowed.
2010-07-07s4-dsdb: use ldb_operr() in the dsdb codeAndrew Tridgell1-5/+3
this replaces "return LDB_ERR_OPERATIONS_ERROR" with "return ldb_operr(ldb)" in places in the dsdb code where we don't already explicitly set an error string. This should make is much easier to track down dsdb module bugs that result in an operations error.
2010-06-19s4:instancetype LDB module - "instanceType" is single-valued - MS-ADTS ↵Matthias Dieter Wallnöfer1-2/+12
3.1.1.5.2.2
2010-06-10s4:instancetype LDB module - prevent all types of "instanceType" manipulationMatthias Dieter Wallnöfer1-0/+16
Also on Windows Server you aren't able to change it.
2010-05-04s4/rodc: Fix the callbacks up the stack to handle referrals on modify requestsAnatoliy Atanasov1-0/+4
2010-01-08s4-dsdb: use dsdb_next_callback()Andrew Tridgell1-1/+2
We can't just use the callers callback directly otherwise the ldb_module_done() is never called on the parent request, as the child request is passed to the callback. Pair-Programmed-With: Andrew Bartlett <abartlet@samba.org>
2009-10-21s4:dsdb Rework modules create new partitions at runtimeAndrew Bartlett1-7/+30
This is done by passing an extended operation to the partitions module to extend the @PARTITION record and to extend the in-memory list of partitions. This also splits things up into module parts that belong above and below repl_meta_data Also slit the partitions module into two files due to the complexity of the code Andrew Barltett
2009-10-02s4:dsdb rework instanceType module - put instanceType in provisionAndrew Bartlett1-29/+9
The instanceType needs to be specified in future because that's how the partitions are actually created.
2009-09-22s4-ldbmodules: allow instanceType to be specified by clientsAndrew Tridgell1-0/+6
This is needed for the WSPP ADS testsuite
2009-09-12s4-samdb: internal s4 ldb modules should be GPL not LGPLAndrew Tridgell1-14/+10
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-07-13libds: share UF_ flags between samba3 and 4.Günther Deschner1-1/+1
Guenther
2009-01-30Fix the mess with ldb includes.Simo Sorce1-10/+13
Separate again the public from the private headers. Add a new header specific for modules. Also add service function for modules as now ldb_context and ldb_module are opaque structures for them.
2008-10-24Remove unused include param/param.h.Jelmer Vernooij1-1/+0
2008-09-29LDB ASYNC: samba4 modulesSimo Sorce1-19/+47
2008-02-20Fix use of some modules (needed _PUBLIC_).Jelmer Vernooij1-1/+1
(This used to be commit ce332130ea77159832da23bab760fa26921719e2)
2008-02-20Use struct-based rather than function-based initialization for ldb modules ↵Jelmer Vernooij1-7/+1
everywhere. (This used to be commit 85c96a325867f7bcdb412ebc53f8a47dbf7cd89b)
2008-01-26ldb: Add ldb_oom() calls in a couple of places.Jelmer Vernooij1-0/+2
(This used to be commit 1163c2ad54b122487fa25960b8989f0f6d0b8c64)
2008-01-18Correct authorship of instanceType moduleAndrew Bartlett1-1/+1
Andrew Bartlett (This used to be commit d427cf4fa67e84ccdece9a3fb31d8e89379a86e7)
2008-01-18Add in a new module to handle instanceTypeAndrew Bartlett1-0/+128
This code raided from the repl_meta_data module, which probably needs to be downsized to just handling the replication data. Andrew Bartlett (This used to be commit 2a418f33705a792d9d16cf1d4aa3dcda467e6e04)