summaryrefslogtreecommitdiff
path: root/source4/dsdb/schema/schema_info_attr.c
AgeCommit message (Collapse)AuthorFilesLines
2010-10-21s4-dsdb: moved a bunch of fuctions from schema/schema_info_attr.c to ↵Andrew Tridgell1-268/+0
samdb/ldb_modules/schema_util.c these functions operate on ldb_modules, so they should be in the ldb_modules directory. They also should return ldb errors codes, not WERROR codes, as otherwise the error can be hidden from the ldap caller This re-arrangement fixes a dependency loop in the schema/samdb code. Pair-Programmed-With: Andrew Bartlett <abartlet@samba.org> Pair-Programmed-With: Kamen Mazdrashki <kamenim@samba.org>
2010-09-17s4-schema: Helper func to compare schemaInfo signituresKamen Mazdrashki1-0/+41
2010-09-17s4-dsdb: Add dsdb_schema_info_blob_is_valid() to verify schemaInfo bloblsKamen Mazdrashki1-10/+24
2010-05-18Finish removal of iconv_convenience in public API's.Jelmer Vernooij1-2/+2
2010-04-29s4/dsdb: schemaInfo revision may be 0Kamen Mazdrashki1-5/+1
In case schemaInfo value is still not set, WinAD supplies schemaInfo blob with revision = 0 and GUID_ZERO
2010-04-29s4/dsdb: remove unused dsdb_schema_info_create() functionKamen Mazdrashki1-35/+0
2010-04-29s4/dsdb: Update Schema cache with updated schemaInfo valueKamen Mazdrashki1-4/+9
Error checking is simplified and my leave leeks. I did it this way to make code more readable, and if we get error in those lines, it will be WERR_NOMEM in which case we are in a much deeper troubles than delayed freeing of few bytes.
2010-04-29s4/samldb: Create initial schemaInfo value if it doesn't exists yetKamen Mazdrashki1-7/+30
2010-04-29s4/dsdb: Use default schemaInfo value when no such value is givenKamen Mazdrashki1-0/+22
Having no value for schemaInfo is totally OK as it turns out. In such cases, we should use a default value with all fields set to 0.
2010-04-29Revert "s4/dsdb: Set schemaInfo attribute value during provisioning"Kamen Mazdrashki1-49/+0
This reverts commit 8149094eddebd9a0e8b7c123c2ed54d00164bb26. Windows implementation does not set schemaInfo attribute value until first Schema update request. This way, newly provisioned forest returns no schemaInfo value. I think it won't be bad for us to have this value preset, but I want to mimic Win AD behavior as close as possible.
2010-04-21s4-schema: allow revision numbers of zeroAndrew Tridgell1-6/+3
w2k8r2 sends a revision of zero in the initial schema replication during a net vampire Pair-Programmed-With: Andrew Bartlett <abartlet@samba.org>
2010-04-13Revert "s4:prefer "samdb_*_dn" basedn calls over the "ldb_get_*_dn" functions"Matthias Dieter Wallnöfer1-2/+2
We should use the "ldb_get_*_basedn" calls since they are available in the LDB library.
2010-04-10s4:dsdb Don't use the permissive modify control on schemaInfo updatesAndrew Bartlett1-2/+2
The use of 'replace' is enough to wipe out the old value, whatever it is, we don't need to set 'permissive modify' too. Additionally, this seems to be causing trouble for the OpenLDAP backend Andrew Bartlett
2010-04-09s4/dsdb: Set schemaInfo attribute value during provisioningKamen Mazdrashki1-0/+49
After provisioning new Forest, schemaInfo should be set to a value with revision=1 and current invocation_id
2010-04-09s4/dsdb: split writing of schemaInfo blob in two partsKamen Mazdrashki1-21/+46
ldb_msg preparation is moved into separate function so that it can be used for implementing schemaInfo updates both on module stack (dsdb_module_... functions) and directly on ldb_context
2010-04-09s4/dsdb: Let caller to control if valid invocationId is critical or ↵Kamen Mazdrashki1-1/+6
zero-guid is acceptable
2010-04-09s4/dsdb: dsdb_schema_info object implementationKamen Mazdrashki1-0/+383
generated by cgit (git 2.34.1) at 2024-11-06 00:30:55 +0000