| blob | 5bdc57366da6e5f58e10787f39818b33893b839f |
1 /*
2 ldb database library
4 Copyright (C) Simo Sorce 2004-2008
5 Copyright (C) Andrew Bartlett <abartlet@samba.org> 2005-2013
6 Copyright (C) Andrew Tridgell 2005-2009
7 Copyright (C) Stefan Metzmacher <metze@samba.org> 2007
8 Copyright (C) Matthieu Patou <mat@samba.org> 2010-2011
10 This program is free software; you can redistribute it and/or modify
11 it under the terms of the GNU General Public License as published by
12 the Free Software Foundation; either version 3 of the License, or
13 (at your option) any later version.
15 This program is distributed in the hope that it will be useful,
16 but WITHOUT ANY WARRANTY; without even the implied warranty of
17 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
18 GNU General Public License for more details.
20 You should have received a copy of the GNU General Public License
21 along with this program. If not, see <http://www.gnu.org/licenses/>.
22 */
24 /*
25 * Name: ldb
26 *
27 * Component: ldb repl_meta_data module
28 *
29 * Description: - add a unique objectGUID onto every new record,
30 * - handle whenCreated, whenChanged timestamps
31 * - handle uSNCreated, uSNChanged numbers
32 * - handle replPropertyMetaData attribute
33 *
34 * Author: Simo Sorce
35 * Author: Stefan Metzmacher
36 */
54 #undef DBGC_CLASS
55 #define DBGC_CLASS DBGC_DRS_REPL
57 /* the RMD_VERSION for linked attributes starts from 1 */
58 #define RMD_VERSION_INITIAL 1
60 /*
61 * It's 29/12/9999 at 23:59:59 UTC as specified in MS-ADTS 7.1.1.4.2
62 * Deleted Objects Container
63 */
78 };
84 };
93 /* the controls we pass down */
96 /*
97 * Backlinks for the replmd_add() case (we want to create
98 * backlinks after creating the user, but before the end of
99 * the ADD request)
100 */
103 /* details for the mode where we apply a bunch of inbound replication meessages */
117 };
120 static int replmd_delete_internals(struct ldb_module *module, struct ldb_request *req, bool re_delete);
143 };
151 };
157 {
165 }
167 }
172 }
179 }
181 }
187 }
189 }
194 }
196 }
201 }
207 }
208 }
221 };
223 /* Attributes looked for when updating or deleting, to check for a urgent replication needed */
228 NULL
229 };
234 {
240 }
246 }
247 }
248 }
250 }
253 {
256 }
258 }
262 /*
263 initialise the module
264 allocate the private structure and build the list
265 of partition DNs for use by replmd_notify()
266 */
268 {
281 }
290 }
295 replmd_private->sorted_links
297 SAMBA_COMPATIBLE_FEATURES_ATTR,
298 SAMBA_SORTED_LINKS_FEATURE);
299 }
303 }
305 /*
306 cleanup our per-transaction contexts
307 */
309 {
314 }
323 };
325 /*
326 a ldb_modify request operating on modules below the
327 current module
328 */
332 {
343 }
346 message,
347 NULL,
348 res,
349 ldb_modify_default_callback,
350 parent);
355 }
361 }
363 /* Run the new request */
368 }
372 }
374 /*
375 process a backlinks we accumulated during a transaction, adding and
376 deleting the backlinks from the target objects
377 */
378 static int replmd_process_backlink(struct ldb_module *module, struct la_backlink *bl, struct ldb_request *parent)
379 {
387 /*
388 - find DN of target
389 - find DN of source
390 - construct ldb_message
391 - either an add or a delete
392 */
401 }
408 }
416 /* Filter down to the attributes we want in the backlink */
419 }
421 /* construct a ldb_message for adding/deleting the backlink */
428 }
433 }
436 /* a backlink should never be single valued. Unfortunately the
437 exchange schema has a attribute
438 msExchBridgeheadedLocalConnectorsDNBL which is single
439 valued and a backlink. We need to cope with that by
440 ignoring the single value flag */
445 /* we allow LDB_ERR_NO_SUCH_ATTRIBUTE as success to
446 cope with possible corruption where the backlink has
447 already been removed */
461 }
464 }
466 /*
467 add a backlink to the list of backlinks to add/delete in the prepare
468 commit
470 forward_dn is stolen onto the defereed context
471 */
480 {
488 }
492 /*
493 * windows 2003 has a broken schema where the
494 * definition of msDS-IsDomainFor is missing (which is
495 * supposed to be the backlink of the
496 * msDS-HasDomainNCs attribute
497 */
499 }
509 }
511 /*
512 add a backlink to the list of backlinks to add/delete in the prepare
513 commit
514 */
522 {
529 /*
530 * windows 2003 has a broken schema where the
531 * definition of msDS-IsDomainFor is missing (which is
532 * supposed to be the backlink of the
533 * msDS-HasDomainNCs attribute
534 */
536 }
545 }
548 /*
549 * Callback for most write operations in this module:
550 *
551 * notify the repl task that a object has changed. The notifies are
552 * gathered up in the replmd_private structure then written to the
553 * @REPLCHANGED object in each partition during the prepare_commit
554 */
556 {
573 /*
574 * Remove the current partition control from what we pass up
575 * the chain if it hasn't been requested manually.
576 */
578 partition_ctrl);
579 }
591 }
594 /*
595 * Set at DBG_NOTICE as once these start to happe, they
596 * will happen a lot until resolved, due to repeated
597 * replication. The caller will probably print the
598 * ldb error string anyway.
599 */
605 ac,
606 LDB_CHANGETYPE_ADD,
607 msg);
613 s);
617 }
623 }
627 /*
628 * process our backlink list after an replmd_add(),
629 * creating and deleting backlinks as necessary (this
630 * code is sync). The other cases are handled inline
631 * with the modify.
632 */
638 }
639 }
640 }
646 }
656 }
657 }
665 }
671 }
673 }
679 }
680 }
683 }
684 }
690 }
693 /* free the partition control container here, for the
694 * common path. Other cases will have it cleaned up
695 * eventually with the ares */
699 }
700 }
703 /*
704 * update a @REPLCHANGED record in each partition if there have been
705 * any writes of replicated data in the partition
706 */
708 {
723 }
731 DSDB_EXTENDED_SCHEMA_UPDATE_NOW_OID,
732 ext_res,
733 DSDB_FLAG_NEXT_MODULE,
734 parent);
737 }
739 }
743 }
746 }
749 /*
750 created a replmd_replicated_request context
751 */
754 {
765 }
777 }
779 /* get our invocationId */
786 }
790 }
792 /*
793 add a time element to a record
794 */
796 {
803 }
808 }
813 }
816 /* always set as replace. This works because on add ops, the flag
817 is ignored */
821 }
823 /*
824 add a uint64_t element to a record
825 */
828 {
834 }
839 }
842 /* always set as replace. This works because on add ops, the flag
843 is ignored */
847 }
852 {
853 /*
854 * This assignment seems inoccous, but it is critical for the
855 * system, as we need to do the comparisons as a unsigned
856 * quantity, not signed (enums are signed integers)
857 */
863 }
865 /*
866 * See above regarding this being an unsigned comparison.
867 * Otherwise when the high bit is set on non-standard
868 * attributes, they would end up first, before objectClass
869 * (0).
870 */
872 }
877 {
883 }
885 /* the objectClass attribute is value 0x00000000, so must be first */
891 }
894 }
899 {
900 /* Note this is O(n^2) for the almost-sorted case, which this is */
902 replmd_replPropertyMetaData1_attid_sort);
904 }
909 {
913 /*
914 * TODO: make this faster by caching the dsdb_attribute pointer
915 * on the ldb_messag_element
916 */
921 /*
922 * TODO: remove this check, we should rely on e1 and e2 having valid attribute names
923 * in the schema
924 */
927 }
930 }
932 }
936 {
937 LDB_TYPESAFE_QSORT(msg->elements, msg->num_elements, schema, replmd_ldb_message_element_attid_sort);
938 }
954 /*
955 fix up linked attributes in replmd_add.
956 This involves setting up the right meta-data in extended DN
957 components, and creating backlinks to the object
958 */
963 NTTIME now,
967 {
972 /* We will take a reference to the schema in replmd_add_backlink */
981 "Attribute %s is single valued but "
986 }
993 }
999 }
1006 }
1016 }
1021 parent);
1025 }
1028 }
1033 }
1038 {
1041 /* Calculate an extended DN for any linked attributes */
1045 }
1049 }
1056 }
1057 }
1060 }
1062 /*
1063 intercept add requests
1064 */
1066 {
1074 DATA_BLOB guid_blob_stack;
1081 /*
1082 * The use of a time_t here seems odd, but as the NTTIME
1083 * elements are actually declared as NTTIME_1sec in the IDL,
1084 * getting a higher resolution timestamp is not required.
1085 */
1087 NTTIME now;
1101 /* check if there's a show relax control (used by provision to say 'I know what I'm doing') */
1105 }
1107 /* do not manipulate our control entries */
1110 }
1128 }
1129 /* we remove this attribute as it can be a string and
1130 * will not be treated correctly and then we will re-add
1131 * it later on in the good format */
1133 }
1135 /* a new GUID */
1140 /* This can't fail */
1144 }
1149 }
1153 /* Get a sequence number from the backend */
1158 }
1160 /* we have to copy the message as the caller might have it as a const */
1166 }
1168 /* generated times */
1175 }
1178 }
1180 /*
1181 * remove autogenerated attributes
1182 */
1189 /*
1190 * readd replicated attributes
1191 */
1197 }
1199 /* build the replication meta_data */
1210 }
1220 i++;
1222 }
1231 }
1233 if ((sa->systemFlags & DS_FLAG_ATTR_NOT_REPLICATED) || (sa->systemFlags & DS_FLAG_ATTR_IS_CONSTRUCTED)) {
1234 /* if the attribute is not replicated (0x00000001)
1235 * or constructed (0x00000004) it has no metadata
1236 */
1237 i++;
1239 }
1244 guid_blob,
1249 }
1250 }
1252 /*
1253 * Prepare the context for the backlinks and
1254 * create metadata for the forward links. The
1255 * backlinks are created in
1256 * replmd_op_callback() after the successful
1257 * ADD of the object.
1258 */
1262 extended_dn,
1267 }
1268 /* linked attributes are not stored in
1269 replPropertyMetaData in FL above w2k */
1270 i++;
1272 }
1284 }
1288 /*
1289 * Set the originating_change_time to 29/12/9999 at 23:59:59
1290 * as specified in MS-ADTS 7.1.1.4.2 Deleted Objects Container
1291 */
1295 }
1298 }
1302 ni++;
1305 i++;
1307 }
1312 i++;
1314 }
1317 }
1319 /* fix meta data count */
1322 /*
1323 * sort meta data array
1324 */
1330 }
1332 /* generated NDR encoded values */
1340 }
1342 /*
1343 * add the autogenerated values
1344 */
1350 }
1356 }
1362 }
1368 }
1374 }
1376 /*
1377 * sort the attributes by attid before storing the object
1378 */
1381 /*
1382 * Assert that we do have an objectClass
1383 */
1391 }
1393 REPL_URGENT_ON_CREATE);
1397 msg,
1400 req);
1406 }
1408 /* current partition control is needed by "replmd_op_callback" */
1411 DSDB_CONTROL_CURRENT_PARTITION_OID,
1416 }
1417 }
1424 }
1425 }
1427 /* mark the control done */
1430 }
1431 /* go on with the call chain */
1433 }
1436 /*
1437 * update the replPropertyMetaData for one element
1438 */
1447 NTTIME now,
1451 {
1461 /* allow this to make it possible for dbcheck
1462 to remove bad attributes */
1464 }
1469 }
1473 if ((a->systemFlags & DS_FLAG_ATTR_NOT_REPLICATED) || (a->systemFlags & DS_FLAG_ATTR_IS_CONSTRUCTED)) {
1475 }
1477 /*
1478 * if the attribute's value haven't changed, and this isn't
1479 * just a delete of everything then return LDB_SUCCESS Unless
1480 * we have the provision control or if the attribute is
1481 * interSiteTopologyGenerator as this page explain:
1482 * http://support.microsoft.com/kb/224815 this attribute is
1483 * periodicaly written by the DC responsible for the intersite
1484 * generation in a given site
1485 *
1486 * Unchanged could be deleting or replacing an already-gone
1487 * thing with an unconstrained delete/empty replace or a
1488 * replace with the same value, but not an add with the same
1489 * value because that could be about adding a duplicate (which
1490 * is for someone else to error out on).
1491 */
1495 }
1501 }
1504 /*
1505 * We intentionally skip the version bump when attempting to
1506 * vanish links.
1507 *
1508 * The control is set by dbcheck and expunge-tombstones which
1509 * both attempt to be non-replicating. Otherwise, making an
1510 * alteration to the replication state would trigger a
1511 * broadcast of all expunged objects.
1512 */
1514 }
1519 }
1524 /*
1525 * allow this to make it possible for dbcheck
1526 * to rebuild broken metadata
1527 */
1529 }
1530 }
1533 /*
1534 * First check if we find it under the msDS-IntID,
1535 * then check if we find it under the OID and
1536 * prefixMap ID.
1537 *
1538 * This allows the administrator to simply re-write
1539 * the attributes and so restore replication, which is
1540 * likely what they will try to do.
1541 */
1544 }
1548 }
1549 }
1552 /* linked attributes are not stored in
1553 replPropertyMetaData in FL above w2k, but we do
1554 raise the seqnum for the object */
1558 }
1560 }
1563 /* we need to add a new one */
1569 }
1572 }
1574 /* Get a new sequence number from the backend. We only do this
1575 * if we have a change that requires a new
1576 * replPropertyMetaData element
1577 */
1582 }
1583 }
1596 }
1600 /*
1601 * Set the originating_change_time to 29/12/9999 at 23:59:59
1602 * as specified in MS-ADTS 7.1.1.4.2 Deleted Objects Container
1603 */
1607 }
1610 }
1616 /* Force version to 0 to be overriden later via replication */
1618 }
1621 }
1623 /*
1624 * Bump the replPropertyMetaData version on an attribute, and if it
1625 * has changed (or forced by leaving rdn_old NULL), update the value
1626 * in the entry.
1627 *
1628 * This is important, as calling a modify operation may not change the
1629 * version number if the values appear unchanged, but a rename between
1630 * parents bumps this value.
1631 *
1632 */
1639 NTTIME now,
1642 {
1648 rdn_name;
1654 };
1660 };
1666 }
1667 }
1675 }
1678 {
1686 }
1687 }
1689 }
1691 /*
1692 * update the replPropertyMetaData object each time we modify an
1693 * object. This is needed for DRS replication, as the merge on the
1694 * client is based on this object
1695 */
1703 {
1708 NTTIME now;
1727 }
1733 }
1741 }
1746 }
1750 /* this happens during an initial vampire while
1751 updating the schema */
1754 }
1762 }
1765 }
1767 /* if isDeleted is present and is TRUE, then we consider we are deleting,
1768 * otherwise we consider we are updating */
1775 }
1778 /* In this case the change_replmetadata control was supplied */
1779 /* We check that it's the only attribute that is provided
1780 * (it's a rare case so it's better to keep the code simplier)
1781 * We also check that the highest local_usn is bigger or the same as
1782 * uSNChanged. */
1790 }
1792 DEBUG(0,(__location__ ": changereplmetada control can't be called when deleting an object\n"));
1794 }
1800 }
1807 }
1810 DSDB_FLAG_NEXT_MODULE |
1811 DSDB_SEARCH_SHOW_RECYCLED |
1812 DSDB_SEARCH_SHOW_EXTENDED_DN |
1813 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT |
1818 }
1825 /*
1826 * The test here now allows for a new
1827 * replPropertyMetaData with no change, if was
1828 * just dbcheck re-sorting the values.
1829 */
1835 }
1836 }
1839 /* search for the existing replPropertyMetaDataBlob. We need
1840 * to use REVEAL and ask for DNs in storage format to support
1841 * the check for values being the same in
1842 * replmd_update_rpmd_element()
1843 */
1845 DSDB_FLAG_NEXT_MODULE |
1846 DSDB_SEARCH_SHOW_RECYCLED |
1847 DSDB_SEARCH_SHOW_EXTENDED_DN |
1848 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT |
1852 }
1859 }
1867 }
1873 }
1882 our_invocation_id,
1884 is_forced_rodc,
1885 req);
1888 }
1892 }
1895 i++;
1897 }
1902 i++;
1904 }
1907 }
1908 }
1910 /*
1911 * Assert that we have an objectClass attribute - this is major
1912 * corruption if we don't have this!
1913 */
1916 /*
1917 * Now check if this objectClass means we need to do urgent replication
1918 */
1920 situation)) {
1922 }
1928 }
1930 /*
1931 * replmd_update_rpmd_element has done an update if the
1932 * seq_num is set
1933 */
1938 /*if we are RODC and this is a DRSR update then its ok*/
1947 }
1953 }
1954 }
1960 }
1966 }
1974 }
1981 }
1985 }
1988 }
1991 {
1996 }
1998 }
2000 /*
2001 get a series of message element values as an array of DNs and GUIDs
2002 the result is sorted by GUID
2003 */
2007 {
2015 }
2021 }
2025 NTSTATUS status;
2034 }
2041 /* we got a DN without a GUID - go find the GUID */
2050 }
2052 }
2056 }
2059 }
2064 }
2065 }
2066 /* keep a pointer to the original ldb_val */
2068 }
2071 }
2073 }
2075 /*
2076 * Get a series of trusted message element values. The result is sorted by
2077 * GUID, even though the GUIDs might not be known. That works because we trust
2078 * the database to give us the elements like that if the
2079 * replmd_private->sorted_links flag is set.
2080 *
2081 * We also ensure that the links are in the Functional Level 2003
2082 * linked attributes format.
2083 */
2091 {
2097 }
2100 /* We need to sort the list. This is the slow old path we want
2101 to avoid.
2102 */
2104 parent);
2107 }
2109 /* Here we get a list of 'struct parsed_dns' without the parsing */
2115 }
2119 }
2120 }
2122 /*
2123 * This upgrades links to FL2003 style, and sorts the result
2124 * if that was needed.
2125 *
2126 * TODO: Add a database feature that asserts we have no FL2000
2127 * style links to avoid this check or add a feature that
2128 * uses a similar check to find sorted/unsorted links
2129 * for an on-the-fly upgrade.
2130 */
2134 el,
2135 ldap_oid);
2138 }
2141 }
2143 /*
2144 Return LDB_SUCCESS if a parsed_dn list contains no duplicate values,
2145 otherwise an error code. For compatibility the error code differs depending
2146 on whether or not the attribute is "member".
2148 As always, the parsed_dn list is assumed to be sorted.
2149 */
2153 {
2161 "Linked attribute %s has "
2168 }
2169 }
2170 }
2172 }
2174 /*
2175 build a new extended DN, including all meta data fields
2177 RMD_FLAGS = DSDB_RMD_FLAG_* bits
2178 RMD_ADDTIME = originating_add_time
2179 RMD_INVOCID = originating_invocation_id
2180 RMD_CHANGETIME = originating_change_time
2181 RMD_ORIGINATING_USN = originating_usn
2182 RMD_LOCAL_USN = local_usn
2183 RMD_VERSION = version
2184 */
2189 {
2193 }
2195 static int replmd_update_la_val(TALLOC_CTX *mem_ctx, struct ldb_val *v, struct dsdb_dn *dsdb_dn,
2200 /*
2201 check if any links need upgrading from w2k format
2202 */
2207 {
2211 NTSTATUS status;
2216 ldap_oid);
2219 }
2220 }
2225 /*
2226 * We optimistically assume they are all the same; if
2227 * the first one is fixed, they are all fixed.
2228 *
2229 * If the first one was *not* fixed and we find a
2230 * later one that is, that is an occasion to shout
2231 * with DEBUG(0).
2232 */
2235 }
2239 }
2245 }
2246 }
2249 /* it's an old one that needs upgrading */
2255 }
2256 }
2258 /*
2259 * This sort() is critical for the operation of
2260 * get_parsed_dns_trusted() because callers of this function
2261 * expect a sorted list, and FL2000 style links are not
2262 * sorted. In particular, as well as the upgrade case,
2263 * get_parsed_dns_trusted() is called from
2264 * replmd_delete_remove_link() even in FL2000 mode
2265 *
2266 * We do not normally pay the cost of the qsort() due to the
2267 * early return in the RMD_VERSION found case.
2268 */
2271 }
2273 /*
2274 Sets the value for a linked attribute, including all meta data fields
2276 see replmd_build_la_val for value names
2277 */
2282 {
2290 NTSTATUS status;
2299 }
2305 }
2311 }
2317 }
2322 }
2328 /* get the ADDTIME from the original */
2332 }
2335 }
2340 }
2342 /* use our invocation id */
2346 /* changetime is the current time */
2350 /* update the USN */
2365 }
2369 }
2371 /**
2372 * Updates the value for a linked attribute, including all meta data fields
2373 */
2374 static int replmd_update_la_val(TALLOC_CTX *mem_ctx, struct ldb_val *v, struct dsdb_dn *dsdb_dn,
2378 {
2381 NTSTATUS status;
2383 /*
2384 * We're updating the linked attribute locally, so increase the version
2385 * by 1 so that other DCs will see the change when it gets replicated out
2386 */
2392 }
2396 }
2398 /*
2399 handle adding a linked attribute
2400 */
2411 {
2421 NTTIME now;
2424 /* get the DNs to be added, fully parsed.
2425 *
2426 * We need full parsing because they came off the wire and we don't
2427 * trust them, besides which we need their details to know where to put
2428 * them.
2429 */
2435 }
2437 /* get the existing DNs, lazily parsed */
2445 }
2454 }
2462 }
2464 /*
2465 * For each new value, find where it would go in the list. If there is
2466 * a matching GUID there, we update the existing value; otherwise we
2467 * put it in place.
2468 */
2484 }
2491 NTSTATUS status;
2497 }
2502 }
2504 /*
2505 * Only "<GUID=...><SID=...>" is allowed.
2506 *
2507 * We get the GUID to just to find the old
2508 * value and the SID in order to add it
2509 * to the found value.
2510 */
2516 }
2522 }
2527 /* this is what we expect */
2531 "i[%u] SID NOT MISSING... Attribute %s already "
2544 }
2551 "NO SID PROVIDED... Attribute %s already "
2558 }
2565 }
2572 }
2579 }
2581 /*
2582 * We just replace the existing value...
2583 */
2587 }
2590 /*
2591 * We are trying to add one that exists, which is only
2592 * allowed if it was previously deleted.
2593 *
2594 * When we do undelete a link we change it in place.
2595 * It will be copied across into the right spot in due
2596 * course.
2597 */
2604 "Attribute %s already "
2610 /* error codes for 'member' need to be
2611 special cased */
2616 }
2617 }
2628 }
2632 msg_dn,
2635 schema_attr,
2636 parent);
2640 }
2642 }
2643 /*
2644 * Here we don't have an exact match.
2645 *
2646 * If next is NULL, this one goes beyond the end of the
2647 * existing list, so we need to add all of those ones first.
2648 *
2649 * If next is not NULL, we need to add all the ones before
2650 * next.
2651 */
2655 /* next should have been parsed, but let's make sure */
2661 }
2662 }
2664 }
2666 /* put all the old ones before next on the list */
2669 num_values++;
2670 }
2676 parent);
2677 /* Make the new linked attribute ldb_val. */
2684 }
2685 num_values++;
2689 }
2690 }
2691 /* copy the rest of the old ones (if any) */
2694 num_values++;
2695 }
2700 }
2706 /* we now tell the backend to replace all existing values
2707 with the one we have constructed */
2711 }
2714 /*
2715 handle deleting all active linked attributes
2716 */
2727 {
2737 NTTIME now;
2742 /* there is nothing to delete... */
2744 /* and we're deleting nothing, so that's OK */
2746 }
2748 }
2753 }
2760 }
2769 }
2776 }
2777 }
2779 /* we empty out el->values here to avoid damage if we return early. */
2783 /*
2784 * If vanish links is set, we are actually removing members of
2785 * old_el->values; otherwise we are just marking them deleted.
2786 *
2787 * There is a special case when no values are given: we remove them
2788 * all. When we have the vanish_links control we just have to remove
2789 * the backlinks and change our element to replace the existing values
2790 * with the empty list.
2791 */
2801 }
2802 }
2806 parent);
2810 }
2813 }
2818 }
2828 }
2829 }
2835 }
2836 }
2845 NULL,
2853 }
2866 }
2867 }
2877 "attribute %s to %s, because "
2880 }
2881 }
2883 /* remove the backlink */
2885 replmd_private,
2887 msg_dn,
2890 parent);
2894 }
2896 /* We flag the deletion and tidy it up later. */
2899 }
2915 }
2916 }
2926 }
2931 parent);
2935 }
2936 }
2947 }
2951 }
2953 j++;
2954 }
2957 }
2959 }
2966 /* we now tell the backend to replace all existing values
2967 with the one we have constructed */
2971 }
2973 /*
2974 handle replacing a linked attribute
2975 */
2986 {
2997 NTTIME now;
3001 /*
3002 * The replace operation is unlike the replace and delete cases in that
3003 * we need to look at every existing link to see whether it is being
3004 * retained or deleted. In other words, we can't avoid parsing the GUIDs.
3005 *
3006 * As we are trying to combine two sorted lists, the algorithm we use
3007 * is akin to the merge phase of a merge sort. We interleave the two
3008 * lists, doing different things depending on which side the current
3009 * item came from.
3010 *
3011 * There are three main cases, with some sub-cases.
3012 *
3013 * - a DN is in the old list but not the new one. It needs to be
3014 * marked as deleted (but left in the list).
3015 * - maybe it is already deleted, and we have less to do.
3016 *
3017 * - a DN is in both lists. The old data gets replaced by the new,
3018 * and the list doesn't grow. The old link may have been marked as
3019 * deleted, in which case we undelete it.
3020 *
3021 * - a DN is in the new list only. We add it in the right place.
3022 */
3029 /* There is nothing to do! */
3031 }
3037 }
3043 }
3050 }
3057 }
3064 }
3076 /* the new list is empty, read the old list */
3081 /* the old list is empty, read new list */
3087 }
3090 /*
3091 * An old ones that come before the next replacement
3092 * (if any). We mark it as deleted and add it to the
3093 * final list.
3094 */
3106 }
3110 msg_dn,
3112 schema_attr,
3113 parent);
3117 }
3118 }
3120 old_i++;
3122 /*
3123 * We are overwriting one. If it was previously
3124 * deleted, we need to add a backlink.
3125 *
3126 * Note that if any RMD_FLAGs in an extended new DN
3127 * will be ignored.
3128 */
3140 }
3146 msg_dn,
3148 schema_attr,
3149 parent);
3153 }
3154 }
3157 old_i++;
3158 new_i++;
3160 /*
3161 * Replacements that don't match an existing one. We
3162 * just add them to the final list.
3163 */
3172 }
3175 msg_dn,
3177 schema_attr,
3178 parent);
3182 }
3184 new_i++;
3185 }
3186 }
3189 }
3197 }
3200 /*
3201 handle linked attributes in modify requests
3202 */
3209 {
3217 /*
3218 * Nothing special is required for modifying or vanishing links
3219 * in fl2000 since they are just strings in a multi-valued
3220 * attribute.
3221 */
3223 DSDB_CONTROL_REPLMD_VANISH_LINKS);
3226 }
3228 }
3230 /*
3231 * TODO:
3232 *
3233 * We should restrict this to the intersection of the list of
3234 * linked attributes in the schema and the list of attributes
3235 * being modified.
3236 *
3237 * This will help performance a little, as otherwise we have
3238 * to allocate the entire object value-by-value.
3239 */
3241 DSDB_FLAG_NEXT_MODULE |
3242 DSDB_SEARCH_SHOW_RECYCLED |
3243 DSDB_SEARCH_REVEAL_INTERNALS |
3244 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT,
3245 parent);
3248 }
3263 }
3266 }
3272 DSDB_CONTROL_REPLMD_VANISH_LINKS);
3276 }
3278 DSDB_CONTROL_DBCHECK);
3281 }
3282 }
3284 /* Odd is for the target. Illegal to modify */
3288 }
3296 parent);
3303 parent);
3310 parent);
3317 }
3322 /* Return codes as found on Windows 2012r2 */
3327 }
3330 }
3334 }
3337 }
3342 /* TODO: this relises a bit too heavily on the exact
3343 behaviour of ldb_msg_find_element and
3344 ldb_msg_remove_element */
3348 i--;
3349 }
3350 }
3354 }
3360 {
3366 WERROR werr;
3379 server_dn);
3380 }
3381 }
3385 }
3388 domain,
3393 }
3396 }
3400 {
3418 /* do not manipulate our control entries */
3421 }
3424 DSDB_CONTROL_SEC_DESC_PROPAGATION_OID);
3428 }
3433 }
3436 }
3441 DSDB_CONTROL_DBCHECK_FIX_DUPLICATE_LINKS);
3448 }
3452 }
3457 }
3463 }
3467 }
3471 }
3474 DSDB_CONTROL_DBCHECK_FIX_LINK_DN_NAME);
3481 }
3485 }
3489 }
3493 }
3497 }
3502 }
3507 }
3513 }
3517 }
3521 }
3523 /*
3524 * If we are run from dbcheck and we are not updating
3525 * a link (as these would need to be sorted and so
3526 * can't go via such a simple update, then do not
3527 * trigger replicated updates and a new USN from this
3528 * change, it wasn't a real change, just a new
3529 * (correct) string DN
3530 */
3534 }
3543 }
3548 }
3552 /* we have to copy the message as the caller might have it as a const */
3558 }
3561 DSDB_CONTROL_DBCHECK_FIX_LINK_DN_SID);
3568 }
3573 }
3578 }
3585 }
3590 }
3596 }
3611 }
3616 }
3618 handle_linked_attribs:
3624 }
3626 /* TODO:
3627 * - replace the old object with the newly constructed one
3628 */
3633 msg,
3636 req);
3641 }
3643 /* current partition control is needed by "replmd_op_callback" */
3646 DSDB_CONTROL_CURRENT_PARTITION_OID,
3651 }
3652 }
3654 /* If we are in functional level 2000, then
3655 * replmd_modify_handle_linked_attribs will have done
3656 * nothing */
3662 }
3663 }
3667 /* we only change whenChanged and uSNChanged if the seq_num
3668 has changed */
3675 }
3682 }
3683 }
3685 /* go on with the call chain */
3687 }
3691 /*
3692 handle a rename request
3694 On a rename we need to do an extra ldb_modify which sets the
3695 whenChanged and uSNChanged attributes. We do this in a callback after the success.
3696 */
3698 {
3704 /* do not manipulate our control entries */
3707 }
3716 }
3728 }
3730 /* go on with the call chain */
3732 }
3734 /* After the rename is compleated, update the whenchanged etc */
3736 {
3759 }
3766 LDB_ERR_OPERATIONS_ERROR);
3767 }
3769 /* TODO:
3770 * - replace the old object with the newly constructed one
3771 */
3777 }
3788 }
3790 /* normalize the rdn attribute name */
3796 }
3804 }
3810 }
3815 }
3820 }
3825 }
3827 /*
3828 * here we let replmd_update_rpmd() only search for
3829 * the existing "replPropertyMetaData" and rdn_name attributes.
3830 *
3831 * We do not want the existing "name" attribute as
3832 * the "name" attribute needs to get the version
3833 * updated on rename even if the rdn value hasn't changed.
3834 *
3835 * This is the diff of the meta data, for a moved user
3836 * on a w2k8r2 server:
3837 *
3838 * # record 1
3839 * -dn: CN=sdf df,CN=Users,DC=bla,DC=base
3840 * +dn: CN=sdf df,OU=TestOU,DC=bla,DC=base
3841 * replPropertyMetaData: NDR: struct replPropertyMetaDataBlob
3842 * version : 0x00000001 (1)
3843 * reserved : 0x00000000 (0)
3844 * @@ -66,11 +66,11 @@ replPropertyMetaData: NDR: struct re
3845 * local_usn : 0x00000000000037a5 (14245)
3846 * array: struct replPropertyMetaData1
3847 * attid : DRSUAPI_ATTID_name (0x90001)
3848 * - version : 0x00000001 (1)
3849 * - originating_change_time : Wed Feb 9 17:20:49 2011 CET
3850 * + version : 0x00000002 (2)
3851 * + originating_change_time : Wed Apr 6 15:21:01 2011 CEST
3852 * originating_invocation_id: 0d36ca05-5507-4e62-aca3-354bab0d39e1
3853 * - originating_usn : 0x00000000000037a5 (14245)
3854 * - local_usn : 0x00000000000037a5 (14245)
3855 * + originating_usn : 0x0000000000003834 (14388)
3856 * + local_usn : 0x0000000000003834 (14388)
3857 * array: struct replPropertyMetaData1
3858 * attid : DRSUAPI_ATTID_userAccountControl (0x90008)
3859 * version : 0x00000004 (4)
3860 */
3874 }
3879 }
3886 }
3890 msg,
3893 req);
3898 }
3900 /* current partition control is needed by "replmd_op_callback" */
3903 DSDB_CONTROL_CURRENT_PARTITION_OID,
3908 }
3909 }
3918 }
3925 }
3927 /* go on with the call chain - do the modify after the rename */
3929 }
3931 /*
3932 * remove links from objects that point at this object when an object
3933 * is deleted. We remove it from the NEXT module per MS-DRSR 5.160
3934 * RemoveObj which states that link removal due to the object being
3935 * deleted is NOT an originating update - they just go away!
3936 *
3937 */
3946 {
3969 }
3975 }
3977 /* remove the link */
3983 }
3991 }
4000 }
4004 DSDB_FLAG_NEXT_MODULE |
4005 DSDB_SEARCH_SHOW_EXTENDED_DN |
4006 DSDB_SEARCH_SHOW_RECYCLED,
4007 parent);
4012 }
4020 }
4022 /*
4023 * This call 'upgrades' the links in link_dns, but we
4024 * do not commit the result back into the database, so
4025 * this is safe to call in FL2000 or on databases that
4026 * have been run at that level in the past.
4027 */
4034 }
4044 }
4048 "Failed to find forward link on %s "
4056 }
4059 /* This needs to get the Binary DN, by first searching */
4067 /*
4068 * Ensure that we tell the modification to vanish any linked
4069 * attributes (not simply mark them as isDeleted = TRUE)
4070 */
4077 }
4078 }
4081 }
4084 /*
4085 handle update of replication meta data for deletion of objects
4087 This also handles the mapping of delete to a rename operation
4088 to allow deletes to be replicated.
4090 It also handles the incoming deleted objects, to ensure they are
4091 fully deleted here. In that case re_delete is true, and we do not
4092 use this as a signal to change the deleted state, just reinforce it.
4094 */
4095 static int replmd_delete_internals(struct ldb_module *module, struct ldb_request *req, bool re_delete)
4096 {
4110 /* yes, this really is a hard coded list. See MS-ADTS
4111 section 3.1.1.5.5.1.1 */
4153 NULL
4154 };
4156 DSDB_SECRET_ATTRIBUTES,
4158 NULL
4159 };
4167 }
4169 /*
4170 * We have to allow dbcheck to remove an object that
4171 * is beyond repair, and to do so totally. This could
4172 * mean we we can get a partial object from the other
4173 * DC, causing havoc, so dbcheck suggests
4174 * re-replication first. dbcheck sets both DBCHECK
4175 * and RELAX in this situation.
4176 */
4179 /* really, really remove it */
4181 }
4187 }
4193 }
4197 /* we need the complete msg off disk, so we can work out which
4198 attributes need to be removed */
4200 DSDB_FLAG_NEXT_MODULE |
4201 DSDB_SEARCH_SHOW_RECYCLED |
4202 DSDB_SEARCH_REVEAL_INTERNALS |
4212 }
4219 /* This supports us noticing an incoming isDeleted and acting on it */
4223 }
4226 /*
4227 * We have to prevent objects being deleted, even if
4228 * the administrator really wants them gone, as
4229 * without the tombstone, we can get a partial object
4230 * from the other DC, causing havoc.
4231 *
4232 * The only other valid case is when the 180 day
4233 * timeout has expired, when relax is specified.
4234 */
4236 /* it is already deleted - really remove it this time */
4239 }
4245 }
4252 }
4259 }
4263 /* consider the SYSTEM_FLAG_DISALLOW_MOVE_ON_DELETE flag */
4264 disallow_move_on_delete =
4268 /* work out where we will be renaming this object to */
4274 /*
4275 * We should not move objects if we can't find the
4276 * deleted objects DN. Not moving (or otherwise
4277 * harming) the Deleted Objects DN itself is handled
4278 * in the caller.
4279 */
4286 }
4288 /* this is probably an attempted delete on a partition
4289 * that doesn't allow delete operations, such as the
4290 * schema partition */
4297 }
4304 }
4305 }
4307 /* get the objects GUID from the search we just did */
4313 ldb,
4314 new_dn,
4316 guid);
4321 }
4329 }
4332 /*
4333 * No matter what has happened with other renames etc, try again to
4334 * get this to be under the deleted DN. See MS-DRSR 5.160 RemoveObj
4335 */
4345 }
4356 }
4357 }
4359 /*
4360 now we need to modify the object in the following ways:
4362 - add isDeleted=TRUE
4363 - update rDN and name, with new rDN
4364 - remove linked attributes
4365 - remove objectCategory and sAMAccountType
4366 - remove attribs not on the preserved list
4367 - preserved if in above list, or is rDN
4368 - remove all linked attribs from this object
4369 - remove all links from other objects to this object
4370 - add lastKnownParent
4371 - update replPropertyMetaData?
4373 see MS-ADTS "Tombstone Requirements" section 3.1.1.5.5.1.1
4374 */
4380 /* we need the storage form of the parent GUID */
4383 DSDB_FLAG_NEXT_MODULE |
4384 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT |
4385 DSDB_SEARCH_REVEAL_INTERNALS|
4389 "repmd_delete: Failed to %s %s, "
4397 }
4399 /*
4400 * Now we can use the DB version,
4401 * it will have the extended DN info in it
4402 */
4405 parent_dn,
4410 }
4413 parent_dn_str);
4416 ": Failed to add lastKnownParent "
4421 }
4428 ": Failed to add msDS-LastKnownRDN "
4433 }
4435 }
4436 }
4443 /*
4444 * MS-ADTS 3.1.1.5.5.1.1 Tombstone Requirements
4445 * describes what must be removed from a tombstone
4446 * object
4447 *
4448 * MS-ADTS 3.1.1.5.5.1.3 Recycled-Object Requirements
4449 * describes what must be removed from a recycled
4450 * object
4451 *
4452 */
4454 /*
4455 * we also mark it as recycled, meaning this object can't be
4456 * recovered (we are stripping its attributes).
4457 * This is done only if we have this schema object of course ...
4458 * This behavior is identical to the one of Windows 2008R2 which
4459 * always set the isRecycled attribute, even if the recycle-bin is
4460 * not activated and what ever the forest level is.
4461 */
4469 }
4471 }
4475 /* work out which of the old attributes we will be removing */
4483 }
4485 /* don't remove the rDN */
4487 }
4490 /*
4491 we have a backlink in this object
4492 that needs to be removed. We're not
4493 allowed to remove it directly
4494 however, so we instead setup a
4495 modify to delete the corresponding
4496 forward link
4497 */
4499 replmd_private,
4503 /*
4504 * now we continue, which means we
4505 * won't remove this backlink
4506 * directly
4507 */
4509 }
4515 __location__
4516 ": Failed to remove backlink of "
4519 old_dn_str,
4523 }
4525 /*
4526 * Otherwise vanish the link, we are
4527 * out of sync and the controlling
4528 * object does not have the source
4529 * link any more
4530 */
4537 }
4540 }
4542 /*
4543 * Ensure that we tell the modification to vanish any linked
4544 * attributes (not simply mark them as isDeleted = TRUE)
4545 */
4547 }
4553 }
4554 }
4559 /*
4560 * MS-ADTS 3.1.1.5.5.1.2 Deleted-Object Requirements
4561 * describes what must be removed from a deleted
4562 * object
4563 */
4570 }
4577 }
4583 }
4588 /* work out what the new rdn value is, for updating the
4589 rDN and name fields */
4594 }
4600 }
4607 }
4616 }
4618 }
4619 }
4621 /*
4622 * TODO: Per MS-DRSR 5.160 RemoveObj we should remove links directly, not as an originating update!
4623 *
4624 */
4626 /*
4627 * No matter what has happned with other renames, try again to
4628 * get this to be under the deleted DN.
4629 */
4631 /* now rename onto the new DN */
4640 }
4642 }
4650 }
4655 }
4658 {
4660 }
4664 {
4666 }
4668 static int replmd_replicated_request_werror(struct replmd_replicated_request *ar, WERROR status)
4669 {
4671 /* TODO: do some error mapping */
4673 /* Let the caller know the full WERROR */
4677 }
4683 {
4690 }
4691 }
4693 }
4696 /*
4697 return true if an update is newer than an existing entry
4698 see section 5.11 of MS-ADTS
4699 */
4704 NTTIME current_change_time,
4705 NTTIME update_change_time)
4706 {
4709 }
4712 }
4714 }
4718 {
4725 }
4730 {
4733 /*
4734 * If the new replPropertyMetaData entry for this attribute is
4735 * not provided (this happens in the case where we look for
4736 * ATTID_name, but the name was not changed), then the local
4737 * state is clearly still current, as the remote
4738 * server didn't send it due to being older the high watermark
4739 * USN we sent.
4740 */
4743 }
4746 /*
4747 * if we compare equal then do an
4748 * update. This is used when a client
4749 * asks for a FULL_SYNC, and can be
4750 * used to recover a corrupt
4751 * replica.
4752 *
4753 * This call is a bit tricky, what we
4754 * are doing it turning the 'is_newer'
4755 * call into a 'not is older' by
4756 * swapping cur_m and new_m, and negating the
4757 * outcome.
4758 */
4760 cur_m);
4763 new_m);
4764 }
4766 }
4769 /*
4770 form a DN for a deleted (DEL:) or conflict (CNF:) DN
4771 */
4779 {
4792 }
4794 /*
4795 * TODO: Per MS-ADTS 3.1.1.5.5 Delete Operation
4796 * we should truncate this value to ensure the RDN is not more than 255 chars.
4797 *
4798 * However we MS-ADTS 3.1.1.5.1.2 Naming Constraints indicates that:
4799 *
4800 * "Naming constraints are not enforced for replicated
4801 * updates." so this is safe and we don't have to work out not
4802 * splitting a UTF8 char right now.
4803 */
4806 /*
4807 * sizeof(guid_str.buf) will always be longer than
4808 * strlen(guid_str.buf) but we allocate using this and
4809 * waste the trailing bytes to avoid scaring folks
4810 * with memcpy() using strlen() below
4811 */
4813 deleted_child_rdn_val.data
4823 }
4832 /*
4833 * talloc won't allocate more than 256MB so we can't
4834 * overflow but just to be sure
4835 */
4838 }
4847 /* Now set the value into the RDN, without parsing it */
4849 deleted_child_rdn_val);
4852 }
4855 /*
4856 form a conflict DN
4857 */
4862 {
4872 }
4877 }
4882 rdn_name,
4883 rdn_val,
4887 }
4889 }
4891 /*
4892 form a deleted DN
4893 */
4900 {
4904 rdn_name,
4905 rdn_value,
4906 guid);
4907 }
4910 /*
4911 perform a modify operation which sets the rDN and name attributes to
4912 their current values. This has the effect of changing these
4913 attributes to have been last updated by the current DC. This is
4914 needed to ensure that renames performed as part of conflict
4915 resolution are propogated to other DCs
4916 */
4919 {
4929 }
4935 }
4937 /* normalize the rdn attribute name */
4941 }
4947 }
4951 }
4954 }
4957 }
4960 }
4962 /*
4963 * We have to mark this as a replicated update otherwise
4964 * schema_data may reject a rename in the schema partition
4965 */
4969 req);
4975 }
4981 failed:
4986 }
4989 /*
4990 callback for conflict DN handling where we have renamed the incoming
4991 record. After renaming it, we need to ensure the change of name and
4992 rDN for the incoming record is seen as an originating update by this DC.
4994 This also handles updating lastKnownParent for entries sent to lostAndFound
4995 */
4997 {
5004 /* call the normal callback for everything except success */
5006 }
5017 }
5019 /* perform a modify of the rDN and name of the record */
5024 }
5031 }
5036 ldb_dn_get_extended_linearized(msg, ar->objs->objects[ar->index_current].last_known_parent, 1));
5041 }
5050 }
5052 }
5055 }
5057 /*
5058 callback for replmd_replicated_apply_add()
5059 This copes with the creation of conflict records in the case where
5060 the DN exists, but with a different objectGUID
5061 */
5062 static int replmd_op_possible_conflict_callback(struct ldb_request *req, struct ldb_reply *ares, int (*callback)(struct ldb_request *req, struct ldb_reply *ares))
5063 {
5078 /* call the normal callback for success */
5081 }
5083 /*
5084 * we have a conflict, and need to decide if we will keep the
5085 * new record or the old record
5086 */
5091 /* For failures other than conflicts, fail the whole operation here */
5093 ldb_asprintf_errstring(ldb_module_get_ctx(ar->module), "Failed to locally apply remote add of %s: %s",
5098 LDB_ERR_OPERATIONS_ERROR);
5099 }
5103 ldb_asprintf_errstring(ldb_module_get_ctx(ar->module), "Failed to determine if we are an RODC when attempting to form conflict DN: %s", ldb_errstring(ldb_module_get_ctx(ar->module)));
5105 LDB_ERR_OPERATIONS_ERROR);
5107 }
5110 /*
5111 * We are on an RODC, or were a GC for this
5112 * partition, so we have to fail this until
5113 * someone who owns the partition sorts it
5114 * out
5115 */
5117 "Conflict adding object '%s' from incoming replication as we are read only for the partition. \n"
5122 }
5124 /*
5125 * first we need the replPropertyMetaData attribute from the
5126 * local, conflicting record
5127 */
5129 attrs,
5130 DSDB_FLAG_NEXT_MODULE |
5131 DSDB_SEARCH_SHOW_DELETED |
5137 }
5144 }
5152 }
5156 /*
5157 * we decide which is newer based on the RPMD on the name
5158 * attribute. See [MS-DRSR] ResolveNameConflict.
5159 *
5160 * We expect omd_name to be present, as this is from a local
5161 * search, but while rmd_name should have been given to us by
5162 * the remote server, if it is missing we just prefer the
5163 * local name in
5164 * replmd_replPropertyMetaData1_new_should_be_taken()
5165 */
5169 DEBUG(0,(__location__ ": Failed to find name attribute in local LDB replPropertyMetaData for %s\n",
5172 }
5174 /*
5175 * Should we preserve the current record, and so rename the
5176 * incoming record to be a conflict?
5177 */
5178 rename_incoming_record
5179 = !replmd_replPropertyMetaData1_new_should_be_taken(ar->objs->dsdb_repl_flags & DSDB_REPL_FLAG_PRIORITISE_INCOMING,
5191 }
5199 }
5204 /* re-submit the request, but with the new DN */
5208 /* we are renaming the existing record */
5217 }
5226 }
5239 }
5241 /*
5242 * now we need to ensure that the rename is seen as an
5243 * originating update. We do that with a modify.
5244 */
5248 }
5250 DEBUG(2,(__location__ ": With conflicting record renamed, re-apply replicated creation of '%s'\n",
5252 }
5256 req,
5257 msg,
5259 ar,
5260 callback,
5261 req);
5264 }
5267 /* current partition control needed by "repmd_op_callback" */
5269 DSDB_CONTROL_CURRENT_PARTITION_OID,
5273 }
5276 /* this tells the partition module to make it a
5277 partial replica if creating an NC */
5279 DSDB_CONTROL_PARTIAL_REPLICA,
5283 }
5284 }
5286 /*
5287 * Finally we re-run the add, otherwise the new record won't
5288 * exist, as we are here because of that exact failure!
5289 */
5291 failed:
5293 /* on failure make the caller get the error. This means
5294 * replication will stop with an error, but there is not much
5295 * else we can do.
5296 */
5299 }
5301 ret);
5302 }
5304 /*
5305 callback for replmd_replicated_apply_add()
5306 This copes with the creation of conflict records in the case where
5307 the DN exists, but with a different objectGUID
5308 */
5310 {
5315 /* This is like a conflict DN, where we put the object in LostAndFound
5316 see MS-DRSR 4.1.10.6.10 FindBestParentObject */
5318 }
5321 }
5323 /*
5324 this is called when a new object comes in over DRS
5325 */
5327 {
5338 NTTIME now;
5354 }
5361 }
5363 ret = ldb_msg_add_string(msg, "whenChanged", ar->objs->objects[ar->index_current].when_changed);
5366 }
5371 }
5376 }
5378 /* remove any message elements that have zero values */
5388 }
5394 i--;
5396 }
5397 }
5403 LDB_CHANGETYPE_ADD,
5404 msg);
5407 s));
5414 }
5418 /*
5419 * the meta data array is already sorted by the caller, except
5420 * for the RDN, which needs to be added.
5421 */
5429 ldb_asprintf_errstring(ldb, "%s: error during DRS repl ADD: %s", __func__, ldb_errstring(ldb));
5431 }
5435 ldb_asprintf_errstring(ldb, "%s: error during DRS repl ADD: %s", __func__, ldb_errstring(ldb));
5437 }
5441 }
5447 }
5451 }
5461 }
5462 }
5467 ldb,
5468 ar,
5469 msg,
5471 ar,
5472 replmd_op_add_callback,
5477 /* current partition control needed by "repmd_op_callback" */
5479 DSDB_CONTROL_CURRENT_PARTITION_OID,
5484 /* this tells the partition module to make it a
5485 partial replica if creating an NC */
5487 DSDB_CONTROL_PARTIAL_REPLICA,
5490 }
5493 }
5497 {
5504 LDB_ERR_OPERATIONS_ERROR);
5505 }
5507 /*
5508 * The error NO_SUCH_OBJECT is not expected, unless the search
5509 * base is the partition DN, and that case doesn't happen here
5510 * because then we wouldn't get a parent_guid_value in any
5511 * case.
5512 */
5516 }
5520 {
5528 /* Per MS-DRSR 4.1.10.6.10
5529 * FindBestParentObject we need to move this
5530 * new object under a deleted object to
5531 * lost-and-found */
5537 "No suitable NC root found for %s. "
5538 "We need to move this object because parent object %s "
5545 "Unable to find NC root for %s: %s. "
5546 "We need to move this object because parent object %s "
5552 }
5555 nc_root,
5556 DS_GUID_LOSTANDFOUND_CONTAINER,
5560 "Unable to find LostAndFound Container for %s "
5561 "in partition %s: %s. "
5562 "We need to move this object because parent object %s "
5568 }
5573 parent_dn
5576 }
5584 }
5585 }
5589 }
5591 }
5593 /* we ignore referrals */
5610 }
5612 /*
5613 * This error code is really important, as it
5614 * is the flag back to the callers to retry
5615 * this with DRSUAPI_DRS_GET_ANC, and so get
5616 * the parent objects before the child
5617 * objects
5618 */
5621 }
5627 }
5630 }
5631 }
5635 }
5637 /*
5638 * Look for the parent object, so we put the new object in the right
5639 * place This is akin to NameObject in MS-DRSR - this routine and the
5640 * callbacks find the right parent name, and correct name for this
5641 * object
5642 */
5645 {
5661 }
5662 }
5671 ldb,
5672 ar,
5674 LDB_SCOPE_SUBTREE,
5675 filter,
5676 attrs,
5677 NULL,
5678 ar,
5679 replmd_replicated_apply_search_for_parent_callback,
5684 DSDB_SEARCH_SHOW_RECYCLED|
5685 DSDB_SEARCH_SHOW_DELETED|
5686 DSDB_SEARCH_SHOW_EXTENDED_DN);
5689 }
5692 }
5694 /*
5695 handle renames that come in over DRS replication
5696 */
5701 {
5726 }
5730 ldb_asprintf_errstring(ldb_module_get_ctx(ar->module), "Failed to locally apply remote rename from %s to %s: %s",
5735 }
5743 }
5744 /*
5745 * we have a conflict, and need to decide if we will keep the
5746 * new record or the old record
5747 */
5752 /*
5753 * We are on an RODC, or were a GC for this
5754 * partition, so we have to fail this until
5755 * someone who owns the partition sorts it
5756 * out
5757 */
5759 "Conflict adding object '%s' from incoming replication but we are read only for the partition. \n"
5764 }
5766 /*
5767 * first we need the replPropertyMetaData attribute from the
5768 * old record
5769 */
5771 attrs,
5772 DSDB_FLAG_NEXT_MODULE |
5773 DSDB_SEARCH_SHOW_DELETED |
5779 }
5786 }
5794 }
5798 /*
5799 * we decide which is newer based on the RPMD on the name
5800 * attribute. See [MS-DRSR] ResolveNameConflict.
5801 *
5802 * We expect omd_name to be present, as this is from a local
5803 * search, but while rmd_name should have been given to us by
5804 * the remote server, if it is missing we just prefer the
5805 * local name in
5806 * replmd_replPropertyMetaData1_new_should_be_taken()
5807 */
5811 DEBUG(0,(__location__ ": Failed to find name attribute in local LDB replPropertyMetaData for %s\n",
5814 }
5816 /*
5817 * Should we preserve the current record, and so rename the
5818 * incoming record to be a conflict?
5819 */
5820 rename_incoming_record =
5837 }
5849 }
5854 }
5856 /* we are renaming the existing record */
5863 }
5872 }
5885 }
5887 /*
5888 * now we need to ensure that the rename is seen as an
5889 * originating update. We do that with a modify.
5890 */
5894 }
5896 DEBUG(2,(__location__ ": With conflicting record renamed, re-apply replicated rename '%s' -> '%s'\n",
5909 }
5913 failed:
5914 /*
5915 * On failure make the caller get the error
5916 * This means replication will stop with an error,
5917 * but there is not much else we can do. In the
5918 * LDB_ERR_ENTRY_ALREADY_EXISTS case this is exactly what is
5919 * needed.
5920 */
5923 }
5927 }
5931 {
5954 NTSTATUS nt_status;
5959 NTTIME now;
5972 /* find existing meta data */
5980 }
5984 }
5985 }
5996 s,
6004 rmd)));
6013 }
6020 /*
6021 * Fill in the remote_parent_guid with the GUID or an all-zero
6022 * GUID.
6023 */
6028 }
6030 /*
6031 * To ensure we follow a complex rename chain around, we have
6032 * to confirm that the DN is the same (mostly to confirm the
6033 * RDN) and the parentGUID is the same.
6034 *
6035 * This ensures we keep things under the correct parent, which
6036 * replmd_replicated_handle_rename() will do.
6037 */
6043 /*
6044 * handle renames, even just by case that come in over
6045 * DRS. Changes in the parent DN don't hit us here,
6046 * because the search for a parent will clean up those
6047 * components.
6048 *
6049 * We also have already filtered out the case where
6050 * the peer has an older name to what we have (see
6051 * replmd_replicated_apply_search_callback())
6052 */
6054 }
6063 }
6066 /*
6067 * Set the callback to one that will fix up the name
6068 * metadata on the new conflict DN
6069 */
6071 }
6081 /* first copy the old meta data */
6084 ni++;
6085 }
6088 /* now merge in the new meta data */
6097 }
6104 /* replace the entry */
6110 }
6111 }
6122 }
6125 }
6132 }
6134 /* we don't want to apply this change so remove the attribute */
6136 removed_attrs++;
6140 }
6149 }
6150 }
6161 }
6162 ni++;
6163 }
6165 /*
6166 * finally correct the size of the meta_data array
6167 */
6178 ldb_asprintf_errstring(ldb, "%s: error during DRS repl merge: %s", __func__, ldb_errstring(ldb));
6180 }
6181 }
6182 /*
6183 * sort the new meta data array
6184 */
6187 ldb_asprintf_errstring(ldb, "%s: error during DRS repl merge: %s", __func__, ldb_errstring(ldb));
6189 }
6191 /*
6192 * Work out if this object is deleted, so we can prune any extra attributes. See MS-DRSR 4.1.10.6.9
6193 * UpdateObject.
6194 *
6195 * This also controls SD propagation below
6196 */
6201 }
6205 /*
6206 * check if some replicated attributes left, otherwise skip the ldb_modify() call
6207 */
6213 }
6220 }
6228 }
6229 }
6231 /* create the meta data value */
6237 }
6239 /*
6240 * when we know that we'll modify the record, add the whenChanged, uSNChanged
6241 * and replPopertyMetaData attributes
6242 */
6243 ret = ldb_msg_add_string(msg, "whenChanged", ar->objs->objects[ar->index_current].when_changed);
6246 }
6250 }
6254 }
6258 /* we want to replace the old values */
6267 }
6268 }
6269 }
6275 LDB_CHANGETYPE_MODIFY,
6276 msg);
6280 s));
6289 }
6292 ldb,
6293 ar,
6294 msg,
6296 ar,
6297 callback,
6302 /* current partition control needed by "repmd_op_callback" */
6304 DSDB_CONTROL_CURRENT_PARTITION_OID,
6309 }
6313 {
6320 LDB_ERR_OPERATIONS_ERROR);
6321 }
6326 }
6334 /* we ignore referrals */
6338 {
6350 /*
6351 * This is the ADD case, find the appropriate parent,
6352 * as this object doesn't exist locally:
6353 */
6358 }
6361 }
6363 /*
6364 * Otherwise, in the MERGE case, work out if we are
6365 * attempting a rename, and if so find the parent the
6366 * newly renamed object wants to belong under (which
6367 * may not be the parent in it's attached string DN
6368 */
6373 /* find existing meta data */
6382 }
6386 }
6387 }
6395 "as local object has an all-zero parentGUID attribute, "
6399 }
6401 /*
6402 * now we need to check for double renames. We could have a
6403 * local rename pending which our replication partner hasn't
6404 * received yet. We choose which one wins by looking at the
6405 * attribute stamps on the two objects, the newer one wins.
6406 *
6407 * This also simply applies the correct algorithms for
6408 * determining if a change was made to name at all, or
6409 * if the object has just been renamed under the same
6410 * parent.
6411 */
6415 DEBUG(0,(__location__ ": Failed to find name attribute in local LDB replPropertyMetaData for %s\n",
6418 }
6420 /*
6421 * if there is no name attribute given then we have to assume the
6422 * object we've received has the older name
6423 */
6431 /* Merge on the existing object, with rename */
6446 /*
6447 * Merge on the existing object, force no
6448 * rename (code below just to explain why in
6449 * the DEBUG() logs)
6450 */
6464 }
6473 }
6474 /*
6475 * This assignment ensures that the strcmp()
6476 * and GUID_equal() calls in
6477 * replmd_replicated_apply_merge() avoids the
6478 * rename call
6479 */
6485 }
6488 }
6489 }
6490 }
6494 }
6496 /**
6497 * Stores the linked attributes received in the replication chunk - these get
6498 * applied at the end of the transaction. We also check that each linked
6499 * attribute is valid, i.e. source and target objects are known.
6500 */
6502 {
6514 /* save away the linked attributes for the end of the transaction */
6520 }
6525 }
6531 }
6535 /* we need to steal the non-scalars so they stay
6536 around until the end of the transaction */
6544 }
6547 }
6550 }
6555 {
6569 /*
6570 * Now that we've applied all the objects, check the new linked
6571 * attributes and store them (we apply them in .prepare_commit)
6572 */
6577 }
6579 /* done applying objects, move on to the next stage */
6581 }
6594 ldb,
6595 ar,
6597 LDB_SCOPE_SUBTREE,
6598 filter,
6599 attrs,
6600 NULL,
6601 ar,
6602 replmd_replicated_apply_search_callback,
6610 }
6613 }
6615 /*
6616 * This is essentially a wrapper for replmd_replicated_apply_next()
6617 *
6618 * This is needed to ensure that both codepaths call this handler.
6619 */
6621 {
6626 if (ar->isDeleted && (ret != LDB_SUCCESS || ldb_dn_compare(msg->dn, deleted_objects_dn) != 0)) {
6627 /*
6628 * Do a delete here again, so that if there is
6629 * anything local that conflicts with this
6630 * object being deleted, it is removed. This
6631 * includes links. See MS-DRSR 4.1.10.6.9
6632 * UpdateObject.
6633 *
6634 * If the object is already deleted, and there
6635 * is no more work required, it doesn't do
6636 * anything.
6637 */
6639 /* This has been updated to point to the DN we eventually did the modify on */
6648 }
6655 }
6657 /* Build a delete request, which hopefully will artually turn into nothing */
6660 NULL,
6661 res,
6662 ldb_modify_default_callback,
6668 }
6670 /*
6671 * This is the guts of the call, call back
6672 * into our delete code, but setting the
6673 * re_delete flag so we delete anything that
6674 * shouldn't be there on a deleted or recycled
6675 * object
6676 */
6680 }
6685 }
6686 }
6690 }
6694 {
6702 LDB_ERR_OPERATIONS_ERROR);
6703 }
6707 }
6712 LDB_ERR_OPERATIONS_ERROR);
6713 }
6718 }
6721 {
6740 NTTIME now;
6754 /* this happens for a REPL_OBJ call where we are
6755 creating the target object by replicating it. The
6756 subdomain join code does this for the partition DN
6757 */
6760 }
6767 }
6769 /*
6770 * first create the new replUpToDateVector
6771 */
6779 }
6783 }
6784 }
6786 /*
6787 * the new uptodateness vector will at least
6788 * contain 1 entry, one for the source_dsa
6789 *
6790 * plus optional values from our old vector and the one from the source_dsa
6791 */
6797 if (!nuv.ctr.ctr2.cursors) return replmd_replicated_request_werror(ar, WERR_NOT_ENOUGH_MEMORY);
6799 /* first copy the old vector */
6802 ni++;
6803 }
6805 /* merge in the source_dsa vector is available */
6812 }
6818 }
6824 }
6826 }
6830 /* if it's not there yet, add it */
6832 ni++;
6833 }
6835 /*
6836 * finally correct the size of the cursors array
6837 */
6840 /*
6841 * sort the cursors
6842 */
6845 /*
6846 * create the change ldb_message
6847 */
6857 }
6861 }
6864 /*
6865 * now create the new repsFrom value from the given repsFromTo1 structure
6866 */
6874 /*
6875 * first see if we already have a repsFrom value for the current source dsa
6876 * if so we'll later replace this value
6877 */
6891 }
6895 }
6897 /*
6898 * we compare the source dsa objectGUID not the invocation_id
6899 * because we want only one repsFrom value per source dsa
6900 * and when the invocation_id of the source dsa has changed we don't need
6901 * the old repsFrom with the old invocation_id
6902 */
6907 }
6912 }
6914 /*
6915 * copy over all old values to the new ldb_message
6916 */
6920 }
6922 /*
6923 * if we haven't found an old repsFrom value for the current source dsa
6924 * we'll add a new value
6925 */
6933 }
6935 /* we now fill the value which is already attached to ldb_message */
6942 }
6944 /*
6945 * the ldb_message_element for the attribute, has all the old values and the new one
6946 * so we'll replace the whole attribute with all values
6947 */
6952 LDB_CHANGETYPE_MODIFY,
6953 msg);
6956 }
6958 /* prepare the ldb_modify() request */
6960 ldb,
6961 ar,
6962 msg,
6964 ar,
6965 replmd_replicated_uptodate_modify_callback,
6971 }
6975 {
6982 LDB_ERR_OPERATIONS_ERROR);
6983 }
6988 }
6996 /* we ignore referrals */
7003 }
7004 }
7008 }
7012 {
7022 NULL
7023 };
7028 /*
7029 * Let the caller know that we did an originating updates
7030 */
7034 ldb,
7035 ar,
7037 LDB_SCOPE_BASE,
7039 attrs,
7040 NULL,
7041 ar,
7042 replmd_replicated_uptodate_search_callback,
7048 }
7052 static int replmd_extended_replicated_objects(struct ldb_module *module, struct ldb_request *req)
7053 {
7066 ldb_debug(ldb, LDB_DEBUG_FATAL, "replmd_extended_replicated_objects: invalid extended data\n");
7068 }
7071 ldb_debug(ldb, LDB_DEBUG_FATAL, "replmd_extended_replicated_objects: extended data invalid version [%u != %u]\n",
7074 }
7080 /* Set the flags to have the replmd_op_callback run over the full set of objects */
7089 }
7097 }
7102 }
7104 /* If this change contained linked attributes in the body
7105 * (rather than in the links section) we need to update
7106 * backlinks in linked_attributes */
7110 }
7116 }
7118 /**
7119 * Checks how to handle an missing target - either we need to fail the
7120 * replication and retry with GET_TGT, ignore the link and continue, or try to
7121 * add a partial link to an unknown target.
7122 */
7132 {
7136 /*
7137 * we may not be able to resolve link targets properly when
7138 * dealing with subsets of objects, e.g. the source is a
7139 * critical object and the target isn't
7140 *
7141 * TODO:
7142 * When we implement Trusted Domains we need to consider
7143 * whether they get treated as an incomplete replica here or not
7144 */
7147 /*
7148 * Ignore the link. We don't increase the highwater-mark in
7149 * the object subset cases, so subsequent replications should
7150 * resolve any missing links
7151 */
7157 }
7161 /*
7162 * target should already be up-to-date so there's no point in
7163 * retrying. This could be due to bad timing, or if a target
7164 * on a one-way link was deleted. We ignore the link rather
7165 * than failing the replication cycle completely
7166 */
7172 }
7175 mem_ctx,
7176 source_dn,
7177 target_dn);
7179 /* fail the replication and retry with GET_TGT */
7181 missing_str,
7186 }
7188 /*
7189 * The target of the cross-partition link is missing. Continue
7190 * and try to at least add the forward-link. This isn't great,
7191 * but a partial link can be fixed by dbcheck, so it's better
7192 * than dropping the link completely.
7193 */
7198 /*
7199 * Only log this when we're actually committing the objects.
7200 * This avoids spurious logs, i.e. if we're just verifying the
7201 * received link during a join.
7202 */
7206 }
7209 }
7211 /**
7212 * Checks that the target object for a linked attribute exists.
7213 * @param guid returns the target object's GUID (is returned)if it exists)
7214 * @param ignore_link set to true if the linked attribute should be ignored
7215 * (i.e. the target doesn't exist, but that it's OK to skip the link)
7216 */
7224 {
7230 NTSTATUS ntstatus;
7240 /*
7241 * This strange behaviour (allowing a NULL/missing
7242 * GUID) originally comes from:
7243 *
7244 * commit e3054ce0fe0f8f62d2f5b2a77893e7a1479128bd
7245 * Author: Andrew Tridgell <tridge@samba.org>
7246 * Date: Mon Dec 21 21:21:55 2009 +1100
7247 *
7248 * s4-drs: cope better with NULL GUIDS from DRS
7249 *
7250 * It is valid to get a NULL GUID over DRS for a deleted forward link. We
7251 * need to match by DN if possible when seeing if we should update an
7252 * existing link.
7253 *
7254 * Pair-Programmed-With: Andrew Bartlett <abartlet@samba.org>
7255 */
7258 DSDB_FLAG_NEXT_MODULE |
7259 DSDB_SEARCH_SHOW_RECYCLED |
7260 DSDB_SEARCH_SEARCH_ALL_PARTITIONS |
7261 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT,
7262 NULL);
7264 ldb_asprintf_errstring(ldb, "Failed to find GUID in linked attribute 0x%x blob for %s from %s",
7273 attrs,
7274 DSDB_FLAG_NEXT_MODULE |
7275 DSDB_SEARCH_SHOW_RECYCLED |
7276 DSDB_SEARCH_SEARCH_ALL_PARTITIONS |
7277 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT,
7278 NULL,
7281 }
7289 }
7293 /*
7294 * target object is unknown. Check whether to ignore the link,
7295 * fail the replication, or add a partial link
7296 */
7311 /* Get the object's state (i.e. Not Deleted, Tombstone, etc) */
7315 /*
7316 * Check for deleted objects as per MS-DRSR 4.1.10.6.14
7317 * ProcessLinkValue(). Link updates should not be sent for
7318 * recycled and tombstone objects (deleting the links should
7319 * happen when we delete the object). This probably means our
7320 * copy of the target object isn't up to date.
7321 */
7324 /*
7325 * target object is deleted. Check whether to ignore the
7326 * link, fail the replication, or add a partial link
7327 */
7333 }
7334 }
7338 }
7340 /**
7341 * Extracts the key details about the source/target object for a
7342 * linked-attribute entry.
7343 * This returns the following details:
7344 * @param ret_attr the schema details for the linked attribute
7345 * @param source_msg the search result for the source object
7346 * @param target_dsdb_dn the unpacked DN info for the target object
7347 */
7354 {
7360 WERROR status;
7364 /*
7365 linked_attributes[0]:
7366 &objs->linked_attributes[i]: struct drsuapi_DsReplicaLinkedAttribute
7367 identifier : *
7368 identifier: struct drsuapi_DsReplicaObjectIdentifier
7369 __ndr_size : 0x0000003a (58)
7370 __ndr_size_sid : 0x00000000 (0)
7371 guid : 8e95b6a9-13dd-4158-89db-3220a5be5cc7
7372 sid : S-0-0
7373 __ndr_size_dn : 0x00000000 (0)
7374 dn : ''
7375 attid : DRSUAPI_ATTID_member (0x1F)
7376 value: struct drsuapi_DsAttributeValue
7377 __ndr_size : 0x0000007e (126)
7378 blob : *
7379 blob : DATA_BLOB length=126
7380 flags : 0x00000001 (1)
7381 1: DRSUAPI_DS_LINKED_ATTRIBUTE_FLAG_ACTIVE
7382 originating_add_time : Wed Sep 2 22:20:01 2009 EST
7383 meta_data: struct drsuapi_DsReplicaMetaData
7384 version : 0x00000015 (21)
7385 originating_change_time : Wed Sep 2 23:39:07 2009 EST
7386 originating_invocation_id: 794640f3-18cf-40ee-a211-a93992b67a64
7387 originating_usn : 0x000000000001e19c (123292)
7389 (for cases where the link is to a normal DN)
7390 &target: struct drsuapi_DsReplicaObjectIdentifier3
7391 __ndr_size : 0x0000007e (126)
7392 __ndr_size_sid : 0x0000001c (28)
7393 guid : 7639e594-db75-4086-b0d4-67890ae46031
7394 sid : S-1-5-21-2848215498-2472035911-1947525656-19924
7395 __ndr_size_dn : 0x00000022 (34)
7396 dn : 'CN=UOne,OU=TestOU,DC=vsofs8,DC=com'
7397 */
7399 /* find the attribute being modified */
7408 }
7415 /*
7416 * get the existing message from the db for the object with
7417 * this GUID, returning attribute being modified. We will then
7418 * use this msg as the basis for a modify call
7419 */
7421 DSDB_FLAG_NEXT_MODULE |
7422 DSDB_SEARCH_SEARCH_ALL_PARTITIONS |
7423 DSDB_SEARCH_SHOW_RECYCLED |
7424 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT |
7425 DSDB_SEARCH_REVEAL_INTERNALS,
7426 NULL,
7430 }
7435 }
7439 /* the value blob for the attribute holds the target object DN */
7447 }
7452 }
7454 /**
7455 * Verifies the source and target objects are known for a linked attribute
7456 */
7459 {
7472 /*
7473 * When we fail to find the source object, the error code we pass
7474 * back here is really important. It flags back to the callers to
7475 * retry this request with DRSUAPI_DRS_GET_ANC. This case should
7476 * never happen if we're replicating from a Samba DC, but it is
7477 * needed to talk to a Windows DC
7478 */
7481 }
7486 }
7488 /*
7489 * We can skip the target object checks if we're only syncing critical
7490 * objects, or we know the target is up-to-date. If either case, we
7491 * still continue even if the target doesn't exist
7492 */
7499 }
7501 /*
7502 * When we fail to find the target object, the error code we pass
7503 * back here is really important. It flags back to the callers to
7504 * retry this request with DRSUAPI_DRS_GET_TGT
7505 */
7508 }
7512 }
7514 /**
7515 * Finds the current active Parsed-DN value for a single-valued linked
7516 * attribute, if one exists.
7517 * @param ret_pdn assigned the active Parsed-DN, or NULL if none was found
7518 * @returns LDB_SUCCESS (regardless of whether a match was found), unless
7519 * an error occurred
7520 */
7527 {
7534 /* nothing to do for multi-valued linked attributes */
7536 }
7542 /* skip any inactive links */
7545 }
7547 /* we've found an active value for this attribute */
7555 }
7558 }
7560 /* no active link found */
7562 }
7564 /**
7565 * @returns true if the replication linked attribute info is newer than we
7566 * already have in our DB
7567 * @param pdn the existing linked attribute info in our DB
7568 * @param la the new linked attribute info received during replication
7569 */
7572 {
7573 /* see if this update is newer than what we have already */
7580 /* no existing info so update is newer */
7582 }
7590 version,
7592 change_time,
7594 }
7596 /**
7597 * Marks an existing linked attribute value as deleted in the DB
7598 * @param pdn the parsed-DN of the target-value to delete
7599 */
7611 {
7614 NTTIME now;
7624 }
7626 /* if the existing link is active, remove its backlink */
7634 }
7635 }
7637 /* mark the existing value as deleted */
7642 }
7644 /**
7645 * Checks for a conflict in single-valued link attributes, and tries to
7646 * resolve the problem if possible.
7647 *
7648 * Single-valued links should only ever have one active value. If we already
7649 * have an active link value, and during replication we receive an active link
7650 * value for a different target DN, then we need to resolve this inconsistency
7651 * and determine which value should be active. If the received info is better/
7652 * newer than the existing link attribute, then we need to set our existing
7653 * link as deleted. If the received info is worse/older, then we should continue
7654 * to add it, but set it as an inactive link.
7655 *
7656 * Note that this is a corner-case that is unlikely to happen (but if it does
7657 * happen, we don't want it to break replication completely).
7658 *
7659 * @param pdn_being_modified the parsed DN corresponding to the received link
7660 * target (note this is NULL if the link does not already exist in our DB)
7661 * @param pdn_list all the source object's Parsed-DNs for this attribute, i.e.
7662 * any existing active or inactive values for the attribute in our DB.
7663 * @param dsdb_dn the target DN for the received link attribute
7664 * @param add_as_inactive gets set to true if the received link is worse than
7665 * the existing link - it should still be added, but as an inactive link.
7666 */
7680 {
7685 /*
7686 * check if there's a conflict for single-valued links, i.e. an active
7687 * linked attribute already exists, but it has a different target value
7688 */
7695 }
7697 /*
7698 * If no active value exists (or the received info is for the currently
7699 * active value), then no conflict exists
7700 */
7703 }
7708 /* Work out how to resolve the conflict based on which info is better */
7716 /*
7717 * Delete our existing active link. The received info will then
7718 * be added (through normal link processing) as the active value
7719 */
7728 }
7734 /*
7735 * we want to keep our existing active link and add the
7736 * received link as inactive
7737 */
7739 }
7742 }
7744 /*
7745 process one linked attribute structure
7746 */
7751 {
7772 /*
7773 * get the attribute being modified, the search result for the source object,
7774 * and the target object's DN details
7775 */
7782 }
7784 /*
7785 * Check for deleted objects per MS-DRSR 4.1.10.6.14
7786 * ProcessLinkValue, because link updates are not applied to
7787 * recycled and tombstone objects. We don't have to delete
7788 * any existing link, that should have happened when the
7789 * object deletion was replicated or initiated.
7790 */
7796 }
7805 }
7808 }
7810 /* parse the existing links */
7817 }
7825 }
7827 /*
7828 * there are some cases where the target object doesn't exist, but it's
7829 * OK to ignore the linked attribute
7830 */
7834 }
7836 /* see if this link already exists */
7847 }
7855 }
7857 /* get a seq_num for this change */
7862 }
7864 /*
7865 * check for single-valued link conflicts, i.e. an active linked
7866 * attribute already exists, but it has a different target value
7867 */
7873 seq_num,
7878 }
7879 }
7885 /* remove the existing backlink */
7887 schema,
7890 parent);
7894 }
7895 }
7903 /*
7904 * We know where the new one needs to be, from the *next
7905 * pointer into pdn_list.
7906 */
7915 }
7916 }
7921 }
7922 }
7929 }
7934 }
7940 }
7942 /* set the link attribute's value to the info that was received */
7952 }
7956 /* Set the new link as inactive/deleted to avoid conflicts */
7960 val_to_update);
7965 }
7969 /* if the new link is active, then add the new backlink */
7971 schema,
7974 parent);
7978 }
7979 }
7981 /* we only change whenChanged and uSNChanged if the seq_num
7982 has changed */
7988 }
7995 }
8001 }
8007 }
8016 tmp_ctx,
8017 LDB_CHANGETYPE_MODIFY,
8018 msg));
8021 }
8026 }
8029 {
8032 }
8035 }
8038 /*
8039 we hook into the transaction operations to allow us to
8040 perform the linked attribute updates at the end of the whole
8041 transaction. This allows a forward linked attribute to be created
8042 before the object is created. During a vampire, w2k8 sends us linked
8043 attributes before the objects they are part of.
8044 */
8046 {
8047 /* create our private structure for this transaction */
8052 /* free any leftover mod_usn records from cancelled
8053 transactions */
8058 }
8063 }
8065 /*
8066 on prepare commit we loop over our queued la_context structures and
8067 apply each of them
8068 */
8070 {
8076 /*
8077 * Walk the list of linked attributes from DRS replication.
8078 *
8079 * We walk backwards, to do the first entry first, as we
8080 * added the entries with DLIST_ADD() which puts them at the
8081 * start of the list
8082 */
8091 }
8092 }
8096 /* possibly change @REPLCHANGED */
8100 }
8103 }
8106 {
8112 }
8126 };
8129 {
8132 }