| blob | c7aacd83615c5a3d26eda63a68e0dcab38334724 |
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 */
115 };
118 static int replmd_delete_internals(struct ldb_module *module, struct ldb_request *req, bool re_delete);
141 };
149 };
155 {
163 }
165 }
170 }
177 }
179 }
185 }
187 }
192 }
194 }
199 }
205 }
206 }
219 };
221 /* Attributes looked for when updating or deleting, to check for a urgent replication needed */
226 NULL
227 };
232 {
238 }
244 }
245 }
246 }
248 }
251 {
254 }
256 }
260 /*
261 initialise the module
262 allocate the private structure and build the list
263 of partition DNs for use by replmd_notify()
264 */
266 {
279 }
288 }
293 replmd_private->sorted_links
295 SAMBA_COMPATIBLE_FEATURES_ATTR,
296 SAMBA_SORTED_LINKS_FEATURE);
297 }
301 }
303 /*
304 cleanup our per-transaction contexts
305 */
307 {
312 }
321 };
323 /*
324 a ldb_modify request operating on modules below the
325 current module
326 */
330 {
341 }
344 message,
345 NULL,
346 res,
347 ldb_modify_default_callback,
348 parent);
353 }
359 }
361 /* Run the new request */
366 }
370 }
372 /*
373 process a backlinks we accumulated during a transaction, adding and
374 deleting the backlinks from the target objects
375 */
376 static int replmd_process_backlink(struct ldb_module *module, struct la_backlink *bl, struct ldb_request *parent)
377 {
385 /*
386 - find DN of target
387 - find DN of source
388 - construct ldb_message
389 - either an add or a delete
390 */
399 }
406 }
414 /* Filter down to the attributes we want in the backlink */
417 }
419 /* construct a ldb_message for adding/deleting the backlink */
426 }
431 }
434 /* a backlink should never be single valued. Unfortunately the
435 exchange schema has a attribute
436 msExchBridgeheadedLocalConnectorsDNBL which is single
437 valued and a backlink. We need to cope with that by
438 ignoring the single value flag */
443 /* we allow LDB_ERR_NO_SUCH_ATTRIBUTE as success to
444 cope with possible corruption where the backlink has
445 already been removed */
459 }
462 }
464 /*
465 add a backlink to the list of backlinks to add/delete in the prepare
466 commit
468 forward_dn is stolen onto the defereed context
469 */
478 {
486 }
490 /*
491 * windows 2003 has a broken schema where the
492 * definition of msDS-IsDomainFor is missing (which is
493 * supposed to be the backlink of the
494 * msDS-HasDomainNCs attribute
495 */
497 }
507 }
509 /*
510 add a backlink to the list of backlinks to add/delete in the prepare
511 commit
512 */
520 {
527 /*
528 * windows 2003 has a broken schema where the
529 * definition of msDS-IsDomainFor is missing (which is
530 * supposed to be the backlink of the
531 * msDS-HasDomainNCs attribute
532 */
534 }
543 }
546 /*
547 * Callback for most write operations in this module:
548 *
549 * notify the repl task that a object has changed. The notifies are
550 * gathered up in the replmd_private structure then written to the
551 * @REPLCHANGED object in each partition during the prepare_commit
552 */
554 {
571 /*
572 * Remove the current partition control from what we pass up
573 * the chain if it hasn't been requested manually.
574 */
576 partition_ctrl);
577 }
589 }
592 /*
593 * Set at DBG_NOTICE as once these start to happe, they
594 * will happen a lot until resolved, due to repeated
595 * replication. The caller will probably print the
596 * ldb error string anyway.
597 */
603 ac,
604 LDB_CHANGETYPE_ADD,
605 msg);
611 s);
615 }
621 }
625 /*
626 * process our backlink list after an replmd_add(),
627 * creating and deleting backlinks as necessary (this
628 * code is sync). The other cases are handled inline
629 * with the modify.
630 */
636 }
637 }
638 }
644 }
654 }
655 }
663 }
669 }
671 }
677 }
678 }
681 }
682 }
688 }
691 /* free the partition control container here, for the
692 * common path. Other cases will have it cleaned up
693 * eventually with the ares */
697 }
698 }
701 /*
702 * update a @REPLCHANGED record in each partition if there have been
703 * any writes of replicated data in the partition
704 */
706 {
721 }
729 DSDB_EXTENDED_SCHEMA_UPDATE_NOW_OID,
730 ext_res,
731 DSDB_FLAG_NEXT_MODULE,
732 parent);
735 }
737 }
741 }
744 }
747 /*
748 created a replmd_replicated_request context
749 */
752 {
763 }
775 }
777 /* get our invocationId */
784 }
788 }
790 /*
791 add a time element to a record
792 */
794 {
801 }
806 }
811 }
814 /* always set as replace. This works because on add ops, the flag
815 is ignored */
819 }
821 /*
822 add a uint64_t element to a record
823 */
826 {
832 }
837 }
840 /* always set as replace. This works because on add ops, the flag
841 is ignored */
845 }
850 {
851 /*
852 * This assignment seems inoccous, but it is critical for the
853 * system, as we need to do the comparisons as a unsigned
854 * quantity, not signed (enums are signed integers)
855 */
861 }
863 /*
864 * See above regarding this being an unsigned comparison.
865 * Otherwise when the high bit is set on non-standard
866 * attributes, they would end up first, before objectClass
867 * (0).
868 */
870 }
875 {
881 }
883 /* the objectClass attribute is value 0x00000000, so must be first */
889 }
892 }
897 {
898 /* Note this is O(n^2) for the almost-sorted case, which this is */
900 replmd_replPropertyMetaData1_attid_sort);
902 }
907 {
911 /*
912 * TODO: make this faster by caching the dsdb_attribute pointer
913 * on the ldb_messag_element
914 */
919 /*
920 * TODO: remove this check, we should rely on e1 and e2 having valid attribute names
921 * in the schema
922 */
925 }
928 }
930 }
934 {
935 LDB_TYPESAFE_QSORT(msg->elements, msg->num_elements, schema, replmd_ldb_message_element_attid_sort);
936 }
952 /*
953 fix up linked attributes in replmd_add.
954 This involves setting up the right meta-data in extended DN
955 components, and creating backlinks to the object
956 */
961 NTTIME now,
965 {
970 /* We will take a reference to the schema in replmd_add_backlink */
979 "Attribute %s is single valued but "
984 }
991 }
997 }
1004 }
1014 }
1019 parent);
1023 }
1026 }
1031 }
1036 {
1039 /* Calculate an extended DN for any linked attributes */
1043 }
1047 }
1054 }
1055 }
1058 }
1060 /*
1061 intercept add requests
1062 */
1064 {
1072 DATA_BLOB guid_blob_stack;
1079 /*
1080 * The use of a time_t here seems odd, but as the NTTIME
1081 * elements are actually declared as NTTIME_1sec in the IDL,
1082 * getting a higher resolution timestamp is not required.
1083 */
1085 NTTIME now;
1099 /* check if there's a show relax control (used by provision to say 'I know what I'm doing') */
1103 }
1105 /* do not manipulate our control entries */
1108 }
1126 }
1127 /* we remove this attribute as it can be a string and
1128 * will not be treated correctly and then we will re-add
1129 * it later on in the good format */
1131 }
1133 /* a new GUID */
1138 /* This can't fail */
1142 }
1147 }
1151 /* Get a sequence number from the backend */
1156 }
1158 /* we have to copy the message as the caller might have it as a const */
1164 }
1166 /* generated times */
1173 }
1176 }
1178 /*
1179 * remove autogenerated attributes
1180 */
1187 /*
1188 * readd replicated attributes
1189 */
1195 }
1197 /* build the replication meta_data */
1208 }
1218 i++;
1220 }
1229 }
1231 if ((sa->systemFlags & DS_FLAG_ATTR_NOT_REPLICATED) || (sa->systemFlags & DS_FLAG_ATTR_IS_CONSTRUCTED)) {
1232 /* if the attribute is not replicated (0x00000001)
1233 * or constructed (0x00000004) it has no metadata
1234 */
1235 i++;
1237 }
1242 guid_blob,
1247 }
1248 }
1250 /*
1251 * Prepare the context for the backlinks and
1252 * create metadata for the forward links. The
1253 * backlinks are created in
1254 * replmd_op_callback() after the successful
1255 * ADD of the object.
1256 */
1260 extended_dn,
1265 }
1266 /* linked attributes are not stored in
1267 replPropertyMetaData in FL above w2k */
1268 i++;
1270 }
1282 }
1286 /*
1287 * Set the originating_change_time to 29/12/9999 at 23:59:59
1288 * as specified in MS-ADTS 7.1.1.4.2 Deleted Objects Container
1289 */
1293 }
1296 }
1300 ni++;
1303 i++;
1305 }
1310 i++;
1312 }
1315 }
1317 /* fix meta data count */
1320 /*
1321 * sort meta data array
1322 */
1328 }
1330 /* generated NDR encoded values */
1338 }
1340 /*
1341 * add the autogenerated values
1342 */
1348 }
1354 }
1360 }
1366 }
1372 }
1374 /*
1375 * sort the attributes by attid before storing the object
1376 */
1379 /*
1380 * Assert that we do have an objectClass
1381 */
1389 }
1391 REPL_URGENT_ON_CREATE);
1395 msg,
1398 req);
1404 }
1406 /* current partition control is needed by "replmd_op_callback" */
1409 DSDB_CONTROL_CURRENT_PARTITION_OID,
1414 }
1415 }
1422 }
1423 }
1425 /* mark the control done */
1428 }
1429 /* go on with the call chain */
1431 }
1434 /*
1435 * update the replPropertyMetaData for one element
1436 */
1445 NTTIME now,
1449 {
1459 /* allow this to make it possible for dbcheck
1460 to remove bad attributes */
1462 }
1467 }
1471 if ((a->systemFlags & DS_FLAG_ATTR_NOT_REPLICATED) || (a->systemFlags & DS_FLAG_ATTR_IS_CONSTRUCTED)) {
1473 }
1475 /*
1476 * if the attribute's value haven't changed, and this isn't
1477 * just a delete of everything then return LDB_SUCCESS Unless
1478 * we have the provision control or if the attribute is
1479 * interSiteTopologyGenerator as this page explain:
1480 * http://support.microsoft.com/kb/224815 this attribute is
1481 * periodicaly written by the DC responsible for the intersite
1482 * generation in a given site
1483 *
1484 * Unchanged could be deleting or replacing an already-gone
1485 * thing with an unconstrained delete/empty replace or a
1486 * replace with the same value, but not an add with the same
1487 * value because that could be about adding a duplicate (which
1488 * is for someone else to error out on).
1489 */
1493 }
1499 }
1502 /*
1503 * We intentionally skip the version bump when attempting to
1504 * vanish links.
1505 *
1506 * The control is set by dbcheck and expunge-tombstones which
1507 * both attempt to be non-replicating. Otherwise, making an
1508 * alteration to the replication state would trigger a
1509 * broadcast of all expunged objects.
1510 */
1512 }
1517 }
1522 /*
1523 * allow this to make it possible for dbcheck
1524 * to rebuild broken metadata
1525 */
1527 }
1528 }
1531 /*
1532 * First check if we find it under the msDS-IntID,
1533 * then check if we find it under the OID and
1534 * prefixMap ID.
1535 *
1536 * This allows the administrator to simply re-write
1537 * the attributes and so restore replication, which is
1538 * likely what they will try to do.
1539 */
1542 }
1546 }
1547 }
1550 /* linked attributes are not stored in
1551 replPropertyMetaData in FL above w2k, but we do
1552 raise the seqnum for the object */
1556 }
1558 }
1561 /* we need to add a new one */
1567 }
1570 }
1572 /* Get a new sequence number from the backend. We only do this
1573 * if we have a change that requires a new
1574 * replPropertyMetaData element
1575 */
1580 }
1581 }
1594 }
1598 /*
1599 * Set the originating_change_time to 29/12/9999 at 23:59:59
1600 * as specified in MS-ADTS 7.1.1.4.2 Deleted Objects Container
1601 */
1605 }
1608 }
1614 /* Force version to 0 to be overriden later via replication */
1616 }
1619 }
1621 /*
1622 * Bump the replPropertyMetaData version on an attribute, and if it
1623 * has changed (or forced by leaving rdn_old NULL), update the value
1624 * in the entry.
1625 *
1626 * This is important, as calling a modify operation may not change the
1627 * version number if the values appear unchanged, but a rename between
1628 * parents bumps this value.
1629 *
1630 */
1637 NTTIME now,
1640 {
1646 rdn_name;
1652 };
1658 };
1664 }
1665 }
1673 }
1676 {
1684 }
1685 }
1687 }
1689 /*
1690 * update the replPropertyMetaData object each time we modify an
1691 * object. This is needed for DRS replication, as the merge on the
1692 * client is based on this object
1693 */
1701 {
1706 NTTIME now;
1725 }
1731 }
1739 }
1744 }
1748 /* this happens during an initial vampire while
1749 updating the schema */
1752 }
1760 }
1763 }
1765 /* if isDeleted is present and is TRUE, then we consider we are deleting,
1766 * otherwise we consider we are updating */
1773 }
1776 /* In this case the change_replmetadata control was supplied */
1777 /* We check that it's the only attribute that is provided
1778 * (it's a rare case so it's better to keep the code simplier)
1779 * We also check that the highest local_usn is bigger or the same as
1780 * uSNChanged. */
1788 }
1790 DEBUG(0,(__location__ ": changereplmetada control can't be called when deleting an object\n"));
1792 }
1798 }
1805 }
1808 DSDB_FLAG_NEXT_MODULE |
1809 DSDB_SEARCH_SHOW_RECYCLED |
1810 DSDB_SEARCH_SHOW_EXTENDED_DN |
1811 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT |
1816 }
1823 /*
1824 * The test here now allows for a new
1825 * replPropertyMetaData with no change, if was
1826 * just dbcheck re-sorting the values.
1827 */
1833 }
1834 }
1837 /* search for the existing replPropertyMetaDataBlob. We need
1838 * to use REVEAL and ask for DNs in storage format to support
1839 * the check for values being the same in
1840 * replmd_update_rpmd_element()
1841 */
1843 DSDB_FLAG_NEXT_MODULE |
1844 DSDB_SEARCH_SHOW_RECYCLED |
1845 DSDB_SEARCH_SHOW_EXTENDED_DN |
1846 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT |
1850 }
1857 }
1865 }
1871 }
1880 our_invocation_id,
1882 is_forced_rodc,
1883 req);
1886 }
1890 }
1893 i++;
1895 }
1900 i++;
1902 }
1905 }
1906 }
1908 /*
1909 * Assert that we have an objectClass attribute - this is major
1910 * corruption if we don't have this!
1911 */
1914 /*
1915 * Now check if this objectClass means we need to do urgent replication
1916 */
1918 situation)) {
1920 }
1926 }
1928 /*
1929 * replmd_update_rpmd_element has done an update if the
1930 * seq_num is set
1931 */
1936 /*if we are RODC and this is a DRSR update then its ok*/
1945 }
1951 }
1952 }
1958 }
1964 }
1972 }
1979 }
1983 }
1986 }
1989 {
1994 }
1996 }
1998 /*
1999 get a series of message element values as an array of DNs and GUIDs
2000 the result is sorted by GUID
2001 */
2005 {
2013 }
2019 }
2023 NTSTATUS status;
2032 }
2039 /* we got a DN without a GUID - go find the GUID */
2048 }
2050 }
2054 }
2057 }
2062 }
2063 }
2064 /* keep a pointer to the original ldb_val */
2066 }
2069 }
2071 }
2073 /*
2074 * Get a series of trusted message element values. The result is sorted by
2075 * GUID, even though the GUIDs might not be known. That works because we trust
2076 * the database to give us the elements like that if the
2077 * replmd_private->sorted_links flag is set.
2078 *
2079 * We also ensure that the links are in the Functional Level 2003
2080 * linked attributes format.
2081 */
2089 {
2095 }
2098 /* We need to sort the list. This is the slow old path we want
2099 to avoid.
2100 */
2102 parent);
2105 }
2107 /* Here we get a list of 'struct parsed_dns' without the parsing */
2113 }
2117 }
2118 }
2120 /*
2121 * This upgrades links to FL2003 style, and sorts the result
2122 * if that was needed.
2123 *
2124 * TODO: Add a database feature that asserts we have no FL2000
2125 * style links to avoid this check or add a feature that
2126 * uses a similar check to find sorted/unsorted links
2127 * for an on-the-fly upgrade.
2128 */
2132 el,
2133 ldap_oid);
2136 }
2139 }
2141 /*
2142 Return LDB_SUCCESS if a parsed_dn list contains no duplicate values,
2143 otherwise an error code. For compatibility the error code differs depending
2144 on whether or not the attribute is "member".
2146 As always, the parsed_dn list is assumed to be sorted.
2147 */
2151 {
2159 "Linked attribute %s has "
2166 }
2167 }
2168 }
2170 }
2172 /*
2173 build a new extended DN, including all meta data fields
2175 RMD_FLAGS = DSDB_RMD_FLAG_* bits
2176 RMD_ADDTIME = originating_add_time
2177 RMD_INVOCID = originating_invocation_id
2178 RMD_CHANGETIME = originating_change_time
2179 RMD_ORIGINATING_USN = originating_usn
2180 RMD_LOCAL_USN = local_usn
2181 RMD_VERSION = version
2182 */
2187 {
2191 }
2193 static int replmd_update_la_val(TALLOC_CTX *mem_ctx, struct ldb_val *v, struct dsdb_dn *dsdb_dn,
2198 /*
2199 check if any links need upgrading from w2k format
2200 */
2205 {
2209 NTSTATUS status;
2214 ldap_oid);
2217 }
2218 }
2223 /*
2224 * We optimistically assume they are all the same; if
2225 * the first one is fixed, they are all fixed.
2226 *
2227 * If the first one was *not* fixed and we find a
2228 * later one that is, that is an occasion to shout
2229 * with DEBUG(0).
2230 */
2233 }
2237 }
2243 }
2244 }
2247 /* it's an old one that needs upgrading */
2253 }
2254 }
2256 /*
2257 * This sort() is critical for the operation of
2258 * get_parsed_dns_trusted() because callers of this function
2259 * expect a sorted list, and FL2000 style links are not
2260 * sorted. In particular, as well as the upgrade case,
2261 * get_parsed_dns_trusted() is called from
2262 * replmd_delete_remove_link() even in FL2000 mode
2263 *
2264 * We do not normally pay the cost of the qsort() due to the
2265 * early return in the RMD_VERSION found case.
2266 */
2269 }
2271 /*
2272 Sets the value for a linked attribute, including all meta data fields
2274 see replmd_build_la_val for value names
2275 */
2280 {
2288 NTSTATUS status;
2297 }
2303 }
2309 }
2315 }
2320 }
2326 /* get the ADDTIME from the original */
2330 }
2333 }
2338 }
2340 /* use our invocation id */
2344 /* changetime is the current time */
2348 /* update the USN */
2363 }
2367 }
2369 /**
2370 * Updates the value for a linked attribute, including all meta data fields
2371 */
2372 static int replmd_update_la_val(TALLOC_CTX *mem_ctx, struct ldb_val *v, struct dsdb_dn *dsdb_dn,
2376 {
2379 NTSTATUS status;
2381 /*
2382 * We're updating the linked attribute locally, so increase the version
2383 * by 1 so that other DCs will see the change when it gets replicated out
2384 */
2390 }
2394 }
2396 /*
2397 handle adding a linked attribute
2398 */
2410 {
2421 NTTIME now;
2428 }
2430 /* get the DNs to be added, fully parsed.
2431 *
2432 * We need full parsing because they came off the wire and we don't
2433 * trust them, besides which we need their details to know where to put
2434 * them.
2435 */
2441 }
2443 /* get the existing DNs, lazily parsed */
2451 }
2460 }
2468 }
2470 /*
2471 * For each new value, find where it would go in the list. If there is
2472 * a matching GUID there, we update the existing value; otherwise we
2473 * put it in place.
2474 */
2490 }
2493 /*
2494 * We are trying to add one that exists, which is only
2495 * allowed if it was previously deleted.
2496 *
2497 * When we do undelete a link we change it in place.
2498 * It will be copied across into the right spot in due
2499 * course.
2500 */
2507 "Attribute %s already "
2513 /* error codes for 'member' need to be
2514 special cased */
2519 }
2520 }
2530 }
2533 schema,
2534 msg_dn,
2537 schema_attr,
2538 parent);
2542 }
2544 }
2545 /*
2546 * Here we don't have an exact match.
2547 *
2548 * If next is NULL, this one goes beyond the end of the
2549 * existing list, so we need to add all of those ones first.
2550 *
2551 * If next is not NULL, we need to add all the ones before
2552 * next.
2553 */
2557 /* next should have been parsed, but let's make sure */
2563 }
2564 }
2566 }
2568 /* put all the old ones before next on the list */
2571 num_values++;
2572 }
2578 parent);
2579 /* Make the new linked attribute ldb_val. */
2586 }
2587 num_values++;
2591 }
2592 }
2593 /* copy the rest of the old ones (if any) */
2596 num_values++;
2597 }
2602 }
2608 /* we now tell the backend to replace all existing values
2609 with the one we have constructed */
2613 }
2616 /*
2617 handle deleting all active linked attributes
2618 */
2630 {
2641 NTTIME now;
2648 }
2651 /* there is nothing to delete... */
2653 /* and we're deleting nothing, so that's OK */
2655 }
2657 }
2662 }
2669 }
2678 }
2685 }
2686 }
2688 /* we empty out el->values here to avoid damage if we return early. */
2692 /*
2693 * If vanish links is set, we are actually removing members of
2694 * old_el->values; otherwise we are just marking them deleted.
2695 *
2696 * There is a special case when no values are given: we remove them
2697 * all. When we have the vanish_links control we just have to remove
2698 * the backlinks and change our element to replace the existing values
2699 * with the empty list.
2700 */
2710 }
2711 }
2715 parent);
2719 }
2722 }
2727 }
2736 }
2737 }
2743 }
2744 }
2753 NULL,
2761 }
2774 }
2775 }
2785 "attribute %s to %s, because "
2788 }
2789 }
2791 /* remove the backlink */
2793 replmd_private,
2794 schema,
2795 msg_dn,
2798 parent);
2802 }
2804 /* We flag the deletion and tidy it up later. */
2807 }
2823 }
2824 }
2833 }
2838 parent);
2842 }
2843 }
2850 j++;
2851 }
2852 }
2854 }
2861 /* we now tell the backend to replace all existing values
2862 with the one we have constructed */
2866 }
2868 /*
2869 handle replacing a linked attribute
2870 */
2882 {
2894 NTTIME now;
2901 }
2903 /*
2904 * The replace operation is unlike the replace and delete cases in that
2905 * we need to look at every existing link to see whether it is being
2906 * retained or deleted. In other words, we can't avoid parsing the GUIDs.
2907 *
2908 * As we are trying to combine two sorted lists, the algorithm we use
2909 * is akin to the merge phase of a merge sort. We interleave the two
2910 * lists, doing different things depending on which side the current
2911 * item came from.
2912 *
2913 * There are three main cases, with some sub-cases.
2914 *
2915 * - a DN is in the old list but not the new one. It needs to be
2916 * marked as deleted (but left in the list).
2917 * - maybe it is already deleted, and we have less to do.
2918 *
2919 * - a DN is in both lists. The old data gets replaced by the new,
2920 * and the list doesn't grow. The old link may have been marked as
2921 * deleted, in which case we undelete it.
2922 *
2923 * - a DN is in the new list only. We add it in the right place.
2924 */
2931 /* There is nothing to do! */
2933 }
2939 }
2945 }
2952 }
2959 }
2966 }
2978 /* the new list is empty, read the old list */
2983 /* the old list is empty, read new list */
2989 }
2992 /*
2993 * An old ones that come before the next replacement
2994 * (if any). We mark it as deleted and add it to the
2995 * final list.
2996 */
3002 invocation_id,
3008 }
3011 schema,
3012 msg_dn,
3014 schema_attr,
3015 parent);
3019 }
3020 }
3022 old_i++;
3024 /*
3025 * We are overwriting one. If it was previously
3026 * deleted, we need to add a backlink.
3027 *
3028 * Note that if any RMD_FLAGs in an extended new DN
3029 * will be ignored.
3030 */
3036 invocation_id,
3042 }
3047 schema,
3048 msg_dn,
3050 schema_attr,
3051 parent);
3055 }
3056 }
3059 old_i++;
3060 new_i++;
3062 /*
3063 * Replacements that don't match an existing one. We
3064 * just add them to the final list.
3065 */
3069 invocation_id,
3074 }
3076 schema,
3077 msg_dn,
3079 schema_attr,
3080 parent);
3084 }
3086 new_i++;
3087 }
3088 }
3091 }
3099 }
3102 /*
3103 handle linked attributes in modify requests
3104 */
3110 {
3120 /*
3121 * Nothing special is required for modifying or vanishing links
3122 * in fl2000 since they are just strings in a multi-valued
3123 * attribute.
3124 */
3126 DSDB_CONTROL_REPLMD_VANISH_LINKS);
3129 }
3131 }
3133 /*
3134 * TODO:
3135 *
3136 * We should restrict this to the intersection of the list of
3137 * linked attributes in the schema and the list of attributes
3138 * being modified.
3139 *
3140 * This will help performance a little, as otherwise we have
3141 * to allocate the entire object value-by-value.
3142 */
3144 DSDB_FLAG_NEXT_MODULE |
3145 DSDB_SEARCH_SHOW_RECYCLED |
3146 DSDB_SEARCH_REVEAL_INTERNALS |
3147 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT,
3148 parent);
3151 }
3155 }
3170 }
3173 }
3177 }
3178 /* Odd is for the target. Illegal to modify */
3182 }
3190 parent);
3197 parent);
3204 parent);
3211 }
3216 /* Return codes as found on Windows 2012r2 */
3221 }
3224 }
3228 }
3231 }
3236 /* TODO: this relises a bit too heavily on the exact
3237 behaviour of ldb_msg_find_element and
3238 ldb_msg_remove_element */
3242 i--;
3243 }
3244 }
3248 }
3254 {
3260 WERROR werr;
3273 server_dn);
3274 }
3275 }
3279 }
3282 domain,
3287 }
3290 }
3294 {
3310 /* do not manipulate our control entries */
3313 }
3316 DSDB_CONTROL_SEC_DESC_PROPAGATION_OID);
3320 }
3325 }
3328 }
3333 DSDB_CONTROL_DBCHECK_FIX_DUPLICATE_LINKS);
3340 }
3344 }
3349 }
3355 }
3359 }
3363 }
3372 }
3377 }
3381 /* we have to copy the message as the caller might have it as a const */
3387 }
3402 }
3407 }
3414 }
3416 /* TODO:
3417 * - replace the old object with the newly constructed one
3418 */
3423 msg,
3426 req);
3431 }
3433 /* current partition control is needed by "replmd_op_callback" */
3436 DSDB_CONTROL_CURRENT_PARTITION_OID,
3441 }
3442 }
3444 /* If we are in functional level 2000, then
3445 * replmd_modify_handle_linked_attribs will have done
3446 * nothing */
3452 }
3453 }
3457 /* we only change whenChanged and uSNChanged if the seq_num
3458 has changed */
3465 }
3472 }
3473 }
3475 /* go on with the call chain */
3477 }
3481 /*
3482 handle a rename request
3484 On a rename we need to do an extra ldb_modify which sets the
3485 whenChanged and uSNChanged attributes. We do this in a callback after the success.
3486 */
3488 {
3494 /* do not manipulate our control entries */
3497 }
3506 }
3518 }
3520 /* go on with the call chain */
3522 }
3524 /* After the rename is compleated, update the whenchanged etc */
3526 {
3549 }
3556 LDB_ERR_OPERATIONS_ERROR);
3557 }
3559 /* TODO:
3560 * - replace the old object with the newly constructed one
3561 */
3567 }
3578 }
3580 /* normalize the rdn attribute name */
3586 }
3594 }
3600 }
3605 }
3610 }
3615 }
3617 /*
3618 * here we let replmd_update_rpmd() only search for
3619 * the existing "replPropertyMetaData" and rdn_name attributes.
3620 *
3621 * We do not want the existing "name" attribute as
3622 * the "name" attribute needs to get the version
3623 * updated on rename even if the rdn value hasn't changed.
3624 *
3625 * This is the diff of the meta data, for a moved user
3626 * on a w2k8r2 server:
3627 *
3628 * # record 1
3629 * -dn: CN=sdf df,CN=Users,DC=bla,DC=base
3630 * +dn: CN=sdf df,OU=TestOU,DC=bla,DC=base
3631 * replPropertyMetaData: NDR: struct replPropertyMetaDataBlob
3632 * version : 0x00000001 (1)
3633 * reserved : 0x00000000 (0)
3634 * @@ -66,11 +66,11 @@ replPropertyMetaData: NDR: struct re
3635 * local_usn : 0x00000000000037a5 (14245)
3636 * array: struct replPropertyMetaData1
3637 * attid : DRSUAPI_ATTID_name (0x90001)
3638 * - version : 0x00000001 (1)
3639 * - originating_change_time : Wed Feb 9 17:20:49 2011 CET
3640 * + version : 0x00000002 (2)
3641 * + originating_change_time : Wed Apr 6 15:21:01 2011 CEST
3642 * originating_invocation_id: 0d36ca05-5507-4e62-aca3-354bab0d39e1
3643 * - originating_usn : 0x00000000000037a5 (14245)
3644 * - local_usn : 0x00000000000037a5 (14245)
3645 * + originating_usn : 0x0000000000003834 (14388)
3646 * + local_usn : 0x0000000000003834 (14388)
3647 * array: struct replPropertyMetaData1
3648 * attid : DRSUAPI_ATTID_userAccountControl (0x90008)
3649 * version : 0x00000004 (4)
3650 */
3664 }
3669 }
3676 }
3680 msg,
3683 req);
3688 }
3690 /* current partition control is needed by "replmd_op_callback" */
3693 DSDB_CONTROL_CURRENT_PARTITION_OID,
3698 }
3699 }
3708 }
3715 }
3717 /* go on with the call chain - do the modify after the rename */
3719 }
3721 /*
3722 * remove links from objects that point at this object when an object
3723 * is deleted. We remove it from the NEXT module per MS-DRSR 5.160
3724 * RemoveObj which states that link removal due to the object being
3725 * deleted is NOT an originating update - they just go away!
3726 *
3727 */
3736 {
3759 }
3765 }
3767 /* remove the link */
3773 }
3781 }
3790 }
3794 DSDB_FLAG_NEXT_MODULE |
3795 DSDB_SEARCH_SHOW_EXTENDED_DN,
3796 parent);
3801 }
3809 }
3811 /*
3812 * This call 'upgrades' the links in link_dns, but we
3813 * do not commit the result back into the database, so
3814 * this is safe to call in FL2000 or on databases that
3815 * have been run at that level in the past.
3816 */
3823 }
3833 }
3837 "Failed to find forward link on %s "
3845 }
3848 /* This needs to get the Binary DN, by first searching */
3856 /*
3857 * Ensure that we tell the modification to vanish any linked
3858 * attributes (not simply mark them as isDeleted = TRUE)
3859 */
3866 }
3867 }
3870 }
3873 /*
3874 handle update of replication meta data for deletion of objects
3876 This also handles the mapping of delete to a rename operation
3877 to allow deletes to be replicated.
3879 It also handles the incoming deleted objects, to ensure they are
3880 fully deleted here. In that case re_delete is true, and we do not
3881 use this as a signal to change the deleted state, just reinforce it.
3883 */
3884 static int replmd_delete_internals(struct ldb_module *module, struct ldb_request *req, bool re_delete)
3885 {
3899 /* yes, this really is a hard coded list. See MS-ADTS
3900 section 3.1.1.5.5.1.1 */
3942 NULL
3943 };
3945 DSDB_SECRET_ATTRIBUTES,
3947 NULL
3948 };
3956 }
3958 /*
3959 * We have to allow dbcheck to remove an object that
3960 * is beyond repair, and to do so totally. This could
3961 * mean we we can get a partial object from the other
3962 * DC, causing havoc, so dbcheck suggests
3963 * re-replication first. dbcheck sets both DBCHECK
3964 * and RELAX in this situation.
3965 */
3968 /* really, really remove it */
3970 }
3976 }
3982 }
3986 /* we need the complete msg off disk, so we can work out which
3987 attributes need to be removed */
3989 DSDB_FLAG_NEXT_MODULE |
3990 DSDB_SEARCH_SHOW_RECYCLED |
3991 DSDB_SEARCH_REVEAL_INTERNALS |
4001 }
4008 /* This supports us noticing an incoming isDeleted and acting on it */
4012 }
4015 /*
4016 * We have to prevent objects being deleted, even if
4017 * the administrator really wants them gone, as
4018 * without the tombstone, we can get a partial object
4019 * from the other DC, causing havoc.
4020 *
4021 * The only other valid case is when the 180 day
4022 * timeout has expired, when relax is specified.
4023 */
4025 /* it is already deleted - really remove it this time */
4028 }
4034 }
4041 }
4048 }
4052 /* consider the SYSTEM_FLAG_DISALLOW_MOVE_ON_DELETE flag */
4053 disallow_move_on_delete =
4057 /* work out where we will be renaming this object to */
4063 /*
4064 * We should not move objects if we can't find the
4065 * deleted objects DN. Not moving (or otherwise
4066 * harming) the Deleted Objects DN itself is handled
4067 * in the caller.
4068 */
4075 }
4077 /* this is probably an attempted delete on a partition
4078 * that doesn't allow delete operations, such as the
4079 * schema partition */
4086 }
4093 }
4094 }
4096 /* get the objects GUID from the search we just did */
4102 ldb,
4103 new_dn,
4105 guid);
4110 }
4118 }
4121 /*
4122 * No matter what has happened with other renames etc, try again to
4123 * get this to be under the deleted DN. See MS-DRSR 5.160 RemoveObj
4124 */
4134 }
4145 }
4146 }
4148 /*
4149 now we need to modify the object in the following ways:
4151 - add isDeleted=TRUE
4152 - update rDN and name, with new rDN
4153 - remove linked attributes
4154 - remove objectCategory and sAMAccountType
4155 - remove attribs not on the preserved list
4156 - preserved if in above list, or is rDN
4157 - remove all linked attribs from this object
4158 - remove all links from other objects to this object
4159 - add lastKnownParent
4160 - update replPropertyMetaData?
4162 see MS-ADTS "Tombstone Requirements" section 3.1.1.5.5.1.1
4163 */
4169 /* we need the storage form of the parent GUID */
4172 DSDB_FLAG_NEXT_MODULE |
4173 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT |
4174 DSDB_SEARCH_REVEAL_INTERNALS|
4178 "repmd_delete: Failed to %s %s, "
4186 }
4188 /*
4189 * Now we can use the DB version,
4190 * it will have the extended DN info in it
4191 */
4194 parent_dn,
4199 }
4202 parent_dn_str);
4205 ": Failed to add lastKnownParent "
4210 }
4217 ": Failed to add msDS-LastKnownRDN "
4222 }
4224 }
4225 }
4232 /*
4233 * MS-ADTS 3.1.1.5.5.1.1 Tombstone Requirements
4234 * describes what must be removed from a tombstone
4235 * object
4236 *
4237 * MS-ADTS 3.1.1.5.5.1.3 Recycled-Object Requirements
4238 * describes what must be removed from a recycled
4239 * object
4240 *
4241 */
4243 /*
4244 * we also mark it as recycled, meaning this object can't be
4245 * recovered (we are stripping its attributes).
4246 * This is done only if we have this schema object of course ...
4247 * This behavior is identical to the one of Windows 2008R2 which
4248 * always set the isRecycled attribute, even if the recycle-bin is
4249 * not activated and what ever the forest level is.
4250 */
4258 }
4260 }
4264 /* work out which of the old attributes we will be removing */
4272 }
4274 /* don't remove the rDN */
4276 }
4278 /*
4279 we have a backlink in this object
4280 that needs to be removed. We're not
4281 allowed to remove it directly
4282 however, so we instead setup a
4283 modify to delete the corresponding
4284 forward link
4285 */
4287 replmd_private,
4294 __location__
4295 ": Failed to remove backlink of "
4298 old_dn_str,
4302 }
4303 /* now we continue, which means we
4304 won't remove this backlink
4305 directly
4306 */
4311 }
4314 }
4316 /*
4317 * Ensure that we tell the modification to vanish any linked
4318 * attributes (not simply mark them as isDeleted = TRUE)
4319 */
4321 }
4327 }
4328 }
4333 /*
4334 * MS-ADTS 3.1.1.5.5.1.2 Deleted-Object Requirements
4335 * describes what must be removed from a deleted
4336 * object
4337 */
4344 }
4351 }
4357 }
4362 /* work out what the new rdn value is, for updating the
4363 rDN and name fields */
4368 }
4374 }
4381 }
4390 }
4392 }
4393 }
4395 /*
4396 * TODO: Per MS-DRSR 5.160 RemoveObj we should remove links directly, not as an originating update!
4397 *
4398 */
4400 /*
4401 * No matter what has happned with other renames, try again to
4402 * get this to be under the deleted DN.
4403 */
4405 /* now rename onto the new DN */
4414 }
4416 }
4424 }
4429 }
4432 {
4434 }
4438 {
4440 }
4442 static int replmd_replicated_request_werror(struct replmd_replicated_request *ar, WERROR status)
4443 {
4445 /* TODO: do some error mapping */
4447 /* Let the caller know the full WERROR */
4451 }
4457 {
4464 }
4465 }
4467 }
4470 /*
4471 return true if an update is newer than an existing entry
4472 see section 5.11 of MS-ADTS
4473 */
4478 NTTIME current_change_time,
4479 NTTIME update_change_time)
4480 {
4483 }
4486 }
4488 }
4492 {
4499 }
4504 {
4507 /*
4508 * If the new replPropertyMetaData entry for this attribute is
4509 * not provided (this happens in the case where we look for
4510 * ATTID_name, but the name was not changed), then the local
4511 * state is clearly still current, as the remote
4512 * server didn't send it due to being older the high watermark
4513 * USN we sent.
4514 */
4517 }
4520 /*
4521 * if we compare equal then do an
4522 * update. This is used when a client
4523 * asks for a FULL_SYNC, and can be
4524 * used to recover a corrupt
4525 * replica.
4526 *
4527 * This call is a bit tricky, what we
4528 * are doing it turning the 'is_newer'
4529 * call into a 'not is older' by
4530 * swapping cur_m and new_m, and negating the
4531 * outcome.
4532 */
4534 cur_m);
4537 new_m);
4538 }
4540 }
4543 /*
4544 form a DN for a deleted (DEL:) or conflict (CNF:) DN
4545 */
4553 {
4566 }
4568 /*
4569 * TODO: Per MS-ADTS 3.1.1.5.5 Delete Operation
4570 * we should truncate this value to ensure the RDN is not more than 255 chars.
4571 *
4572 * However we MS-ADTS 3.1.1.5.1.2 Naming Constraints indicates that:
4573 *
4574 * "Naming constraints are not enforced for replicated
4575 * updates." so this is safe and we don't have to work out not
4576 * splitting a UTF8 char right now.
4577 */
4580 /*
4581 * sizeof(guid_str.buf) will always be longer than
4582 * strlen(guid_str.buf) but we allocate using this and
4583 * waste the trailing bytes to avoid scaring folks
4584 * with memcpy() using strlen() below
4585 */
4587 deleted_child_rdn_val.data
4597 }
4606 /*
4607 * talloc won't allocate more than 256MB so we can't
4608 * overflow but just to be sure
4609 */
4612 }
4621 /* Now set the value into the RDN, without parsing it */
4623 deleted_child_rdn_val);
4626 }
4629 /*
4630 form a conflict DN
4631 */
4636 {
4646 }
4651 }
4656 rdn_name,
4657 rdn_val,
4661 }
4663 }
4665 /*
4666 form a deleted DN
4667 */
4674 {
4678 rdn_name,
4679 rdn_value,
4680 guid);
4681 }
4684 /*
4685 perform a modify operation which sets the rDN and name attributes to
4686 their current values. This has the effect of changing these
4687 attributes to have been last updated by the current DC. This is
4688 needed to ensure that renames performed as part of conflict
4689 resolution are propogated to other DCs
4690 */
4693 {
4703 }
4709 }
4711 /* normalize the rdn attribute name */
4715 }
4721 }
4725 }
4728 }
4731 }
4734 }
4736 /*
4737 * We have to mark this as a replicated update otherwise
4738 * schema_data may reject a rename in the schema partition
4739 */
4743 req);
4749 }
4755 failed:
4760 }
4763 /*
4764 callback for conflict DN handling where we have renamed the incoming
4765 record. After renaming it, we need to ensure the change of name and
4766 rDN for the incoming record is seen as an originating update by this DC.
4768 This also handles updating lastKnownParent for entries sent to lostAndFound
4769 */
4771 {
4778 /* call the normal callback for everything except success */
4780 }
4791 }
4793 /* perform a modify of the rDN and name of the record */
4798 }
4805 }
4810 ldb_dn_get_extended_linearized(msg, ar->objs->objects[ar->index_current].last_known_parent, 1));
4815 }
4824 }
4826 }
4829 }
4831 /*
4832 callback for replmd_replicated_apply_add()
4833 This copes with the creation of conflict records in the case where
4834 the DN exists, but with a different objectGUID
4835 */
4836 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))
4837 {
4852 /* call the normal callback for success */
4855 }
4857 /*
4858 * we have a conflict, and need to decide if we will keep the
4859 * new record or the old record
4860 */
4865 /* For failures other than conflicts, fail the whole operation here */
4867 ldb_asprintf_errstring(ldb_module_get_ctx(ar->module), "Failed to locally apply remote add of %s: %s",
4872 LDB_ERR_OPERATIONS_ERROR);
4873 }
4877 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)));
4879 LDB_ERR_OPERATIONS_ERROR);
4881 }
4884 /*
4885 * We are on an RODC, or were a GC for this
4886 * partition, so we have to fail this until
4887 * someone who owns the partition sorts it
4888 * out
4889 */
4891 "Conflict adding object '%s' from incoming replication as we are read only for the partition. \n"
4895 }
4897 /*
4898 * first we need the replPropertyMetaData attribute from the
4899 * local, conflicting record
4900 */
4902 attrs,
4903 DSDB_FLAG_NEXT_MODULE |
4904 DSDB_SEARCH_SHOW_DELETED |
4910 }
4917 }
4925 }
4929 /*
4930 * we decide which is newer based on the RPMD on the name
4931 * attribute. See [MS-DRSR] ResolveNameConflict.
4932 *
4933 * We expect omd_name to be present, as this is from a local
4934 * search, but while rmd_name should have been given to us by
4935 * the remote server, if it is missing we just prefer the
4936 * local name in
4937 * replmd_replPropertyMetaData1_new_should_be_taken()
4938 */
4942 DEBUG(0,(__location__ ": Failed to find name attribute in local LDB replPropertyMetaData for %s\n",
4945 }
4947 /*
4948 * Should we preserve the current record, and so rename the
4949 * incoming record to be a conflict?
4950 */
4951 rename_incoming_record
4952 = !replmd_replPropertyMetaData1_new_should_be_taken(ar->objs->dsdb_repl_flags & DSDB_REPL_FLAG_PRIORITISE_INCOMING,
4964 }
4972 }
4977 /* re-submit the request, but with the new DN */
4981 /* we are renaming the existing record */
4990 }
4999 }
5012 }
5014 /*
5015 * now we need to ensure that the rename is seen as an
5016 * originating update. We do that with a modify.
5017 */
5021 }
5023 DEBUG(2,(__location__ ": With conflicting record renamed, re-apply replicated creation of '%s'\n",
5025 }
5029 req,
5030 msg,
5032 ar,
5033 callback,
5034 req);
5037 }
5040 /* current partition control needed by "repmd_op_callback" */
5042 DSDB_CONTROL_CURRENT_PARTITION_OID,
5046 }
5049 /* this tells the partition module to make it a
5050 partial replica if creating an NC */
5052 DSDB_CONTROL_PARTIAL_REPLICA,
5056 }
5057 }
5059 /*
5060 * Finally we re-run the add, otherwise the new record won't
5061 * exist, as we are here because of that exact failure!
5062 */
5064 failed:
5066 /* on failure make the caller get the error. This means
5067 * replication will stop with an error, but there is not much
5068 * else we can do.
5069 */
5071 ret);
5072 }
5074 /*
5075 callback for replmd_replicated_apply_add()
5076 This copes with the creation of conflict records in the case where
5077 the DN exists, but with a different objectGUID
5078 */
5080 {
5085 /* This is like a conflict DN, where we put the object in LostAndFound
5086 see MS-DRSR 4.1.10.6.10 FindBestParentObject */
5088 }
5091 }
5093 /*
5094 this is called when a new object comes in over DRS
5095 */
5097 {
5108 NTTIME now;
5124 }
5131 }
5133 ret = ldb_msg_add_string(msg, "whenChanged", ar->objs->objects[ar->index_current].when_changed);
5136 }
5141 }
5146 }
5148 /* remove any message elements that have zero values */
5158 }
5164 i--;
5166 }
5167 }
5173 LDB_CHANGETYPE_ADD,
5174 msg);
5177 s));
5184 }
5188 /*
5189 * the meta data array is already sorted by the caller, except
5190 * for the RDN, which needs to be added.
5191 */
5199 ldb_asprintf_errstring(ldb, "%s: error during DRS repl ADD: %s", __func__, ldb_errstring(ldb));
5201 }
5205 ldb_asprintf_errstring(ldb, "%s: error during DRS repl ADD: %s", __func__, ldb_errstring(ldb));
5207 }
5211 }
5217 }
5221 }
5231 }
5232 }
5237 ldb,
5238 ar,
5239 msg,
5241 ar,
5242 replmd_op_add_callback,
5247 /* current partition control needed by "repmd_op_callback" */
5249 DSDB_CONTROL_CURRENT_PARTITION_OID,
5254 /* this tells the partition module to make it a
5255 partial replica if creating an NC */
5257 DSDB_CONTROL_PARTIAL_REPLICA,
5260 }
5263 }
5267 {
5274 LDB_ERR_OPERATIONS_ERROR);
5275 }
5277 /*
5278 * The error NO_SUCH_OBJECT is not expected, unless the search
5279 * base is the partition DN, and that case doesn't happen here
5280 * because then we wouldn't get a parent_guid_value in any
5281 * case.
5282 */
5286 }
5290 {
5298 /* Per MS-DRSR 4.1.10.6.10
5299 * FindBestParentObject we need to move this
5300 * new object under a deleted object to
5301 * lost-and-found */
5307 "No suitable NC root found for %s. "
5308 "We need to move this object because parent object %s "
5315 "Unable to find NC root for %s: %s. "
5316 "We need to move this object because parent object %s "
5322 }
5325 nc_root,
5326 DS_GUID_LOSTANDFOUND_CONTAINER,
5330 "Unable to find LostAndFound Container for %s "
5331 "in partition %s: %s. "
5332 "We need to move this object because parent object %s "
5338 }
5343 parent_dn
5346 }
5354 }
5355 }
5359 }
5361 }
5363 /* we ignore referrals */
5380 }
5382 /*
5383 * This error code is really important, as it
5384 * is the flag back to the callers to retry
5385 * this with DRSUAPI_DRS_GET_ANC, and so get
5386 * the parent objects before the child
5387 * objects
5388 */
5391 }
5397 }
5400 }
5401 }
5405 }
5407 /*
5408 * Look for the parent object, so we put the new object in the right
5409 * place This is akin to NameObject in MS-DRSR - this routine and the
5410 * callbacks find the right parent name, and correct name for this
5411 * object
5412 */
5415 {
5431 }
5432 }
5441 ldb,
5442 ar,
5444 LDB_SCOPE_SUBTREE,
5445 filter,
5446 attrs,
5447 NULL,
5448 ar,
5449 replmd_replicated_apply_search_for_parent_callback,
5454 DSDB_SEARCH_SHOW_RECYCLED|
5455 DSDB_SEARCH_SHOW_DELETED|
5456 DSDB_SEARCH_SHOW_EXTENDED_DN);
5459 }
5462 }
5464 /*
5465 handle renames that come in over DRS replication
5466 */
5471 {
5496 }
5500 ldb_asprintf_errstring(ldb_module_get_ctx(ar->module), "Failed to locally apply remote rename from %s to %s: %s",
5505 }
5513 }
5514 /*
5515 * we have a conflict, and need to decide if we will keep the
5516 * new record or the old record
5517 */
5522 /*
5523 * We are on an RODC, or were a GC for this
5524 * partition, so we have to fail this until
5525 * someone who owns the partition sorts it
5526 * out
5527 */
5529 "Conflict adding object '%s' from incoming replication but we are read only for the partition. \n"
5533 }
5535 /*
5536 * first we need the replPropertyMetaData attribute from the
5537 * old record
5538 */
5540 attrs,
5541 DSDB_FLAG_NEXT_MODULE |
5542 DSDB_SEARCH_SHOW_DELETED |
5548 }
5555 }
5563 }
5567 /*
5568 * we decide which is newer based on the RPMD on the name
5569 * attribute. See [MS-DRSR] ResolveNameConflict.
5570 *
5571 * We expect omd_name to be present, as this is from a local
5572 * search, but while rmd_name should have been given to us by
5573 * the remote server, if it is missing we just prefer the
5574 * local name in
5575 * replmd_replPropertyMetaData1_new_should_be_taken()
5576 */
5580 DEBUG(0,(__location__ ": Failed to find name attribute in local LDB replPropertyMetaData for %s\n",
5583 }
5585 /*
5586 * Should we preserve the current record, and so rename the
5587 * incoming record to be a conflict?
5588 */
5589 rename_incoming_record =
5606 }
5618 }
5623 }
5625 /* we are renaming the existing record */
5632 }
5641 }
5654 }
5656 /*
5657 * now we need to ensure that the rename is seen as an
5658 * originating update. We do that with a modify.
5659 */
5663 }
5665 DEBUG(2,(__location__ ": With conflicting record renamed, re-apply replicated rename '%s' -> '%s'\n",
5678 }
5679 failed:
5681 /*
5682 * On failure make the caller get the error
5683 * This means replication will stop with an error,
5684 * but there is not much else we can do. In the
5685 * LDB_ERR_ENTRY_ALREADY_EXISTS case this is exactly what is
5686 * needed.
5687 */
5691 }
5695 {
5718 NTSTATUS nt_status;
5723 NTTIME now;
5736 /* find existing meta data */
5744 }
5748 }
5749 }
5760 s,
5768 rmd)));
5777 }
5784 /*
5785 * Fill in the remote_parent_guid with the GUID or an all-zero
5786 * GUID.
5787 */
5792 }
5794 /*
5795 * To ensure we follow a complex rename chain around, we have
5796 * to confirm that the DN is the same (mostly to confirm the
5797 * RDN) and the parentGUID is the same.
5798 *
5799 * This ensures we keep things under the correct parent, which
5800 * replmd_replicated_handle_rename() will do.
5801 */
5807 /*
5808 * handle renames, even just by case that come in over
5809 * DRS. Changes in the parent DN don't hit us here,
5810 * because the search for a parent will clean up those
5811 * components.
5812 *
5813 * We also have already filtered out the case where
5814 * the peer has an older name to what we have (see
5815 * replmd_replicated_apply_search_callback())
5816 */
5818 }
5827 }
5830 /*
5831 * Set the callback to one that will fix up the name
5832 * metadata on the new conflict DN
5833 */
5835 }
5845 /* first copy the old meta data */
5848 ni++;
5849 }
5852 /* now merge in the new meta data */
5861 }
5868 /* replace the entry */
5874 }
5875 }
5886 }
5889 }
5896 }
5898 /* we don't want to apply this change so remove the attribute */
5900 removed_attrs++;
5904 }
5913 }
5914 }
5925 }
5926 ni++;
5927 }
5929 /*
5930 * finally correct the size of the meta_data array
5931 */
5942 ldb_asprintf_errstring(ldb, "%s: error during DRS repl merge: %s", __func__, ldb_errstring(ldb));
5944 }
5945 }
5946 /*
5947 * sort the new meta data array
5948 */
5951 ldb_asprintf_errstring(ldb, "%s: error during DRS repl merge: %s", __func__, ldb_errstring(ldb));
5953 }
5955 /*
5956 * Work out if this object is deleted, so we can prune any extra attributes. See MS-DRSR 4.1.10.6.9
5957 * UpdateObject.
5958 *
5959 * This also controls SD propagation below
5960 */
5965 }
5969 /*
5970 * check if some replicated attributes left, otherwise skip the ldb_modify() call
5971 */
5977 }
5984 }
5992 }
5993 }
5995 /* create the meta data value */
6001 }
6003 /*
6004 * when we know that we'll modify the record, add the whenChanged, uSNChanged
6005 * and replPopertyMetaData attributes
6006 */
6007 ret = ldb_msg_add_string(msg, "whenChanged", ar->objs->objects[ar->index_current].when_changed);
6010 }
6014 }
6018 }
6022 /* we want to replace the old values */
6031 }
6032 }
6033 }
6039 LDB_CHANGETYPE_MODIFY,
6040 msg);
6044 s));
6053 }
6056 ldb,
6057 ar,
6058 msg,
6060 ar,
6061 callback,
6066 /* current partition control needed by "repmd_op_callback" */
6068 DSDB_CONTROL_CURRENT_PARTITION_OID,
6073 }
6077 {
6084 LDB_ERR_OPERATIONS_ERROR);
6085 }
6090 }
6098 /* we ignore referrals */
6102 {
6114 /*
6115 * This is the ADD case, find the appropriate parent,
6116 * as this object doesn't exist locally:
6117 */
6122 }
6125 }
6127 /*
6128 * Otherwise, in the MERGE case, work out if we are
6129 * attempting a rename, and if so find the parent the
6130 * newly renamed object wants to belong under (which
6131 * may not be the parent in it's attached string DN
6132 */
6137 /* find existing meta data */
6146 }
6150 }
6151 }
6159 "as local object has an all-zero parentGUID attribute, "
6163 }
6165 /*
6166 * now we need to check for double renames. We could have a
6167 * local rename pending which our replication partner hasn't
6168 * received yet. We choose which one wins by looking at the
6169 * attribute stamps on the two objects, the newer one wins.
6170 *
6171 * This also simply applies the correct algorithms for
6172 * determining if a change was made to name at all, or
6173 * if the object has just been renamed under the same
6174 * parent.
6175 */
6179 DEBUG(0,(__location__ ": Failed to find name attribute in local LDB replPropertyMetaData for %s\n",
6182 }
6184 /*
6185 * if there is no name attribute given then we have to assume the
6186 * object we've received has the older name
6187 */
6195 /* Merge on the existing object, with rename */
6210 /*
6211 * Merge on the existing object, force no
6212 * rename (code below just to explain why in
6213 * the DEBUG() logs)
6214 */
6228 }
6237 }
6238 /*
6239 * This assignment ensures that the strcmp()
6240 * and GUID_equal() calls in
6241 * replmd_replicated_apply_merge() avoids the
6242 * rename call
6243 */
6249 }
6252 }
6253 }
6254 }
6258 }
6260 /**
6261 * Stores the linked attributes received in the replication chunk - these get
6262 * applied at the end of the transaction. We also check that each linked
6263 * attribute is valid, i.e. source and target objects are known.
6264 */
6266 {
6278 /* save away the linked attributes for the end of the transaction */
6284 }
6289 }
6295 }
6299 /* we need to steal the non-scalars so they stay
6300 around until the end of the transaction */
6308 }
6311 }
6314 }
6319 {
6333 /*
6334 * Now that we've applied all the objects, check the new linked
6335 * attributes and store them (we apply them in .prepare_commit)
6336 */
6341 }
6343 /* done applying objects, move on to the next stage */
6345 }
6358 ldb,
6359 ar,
6361 LDB_SCOPE_SUBTREE,
6362 filter,
6363 attrs,
6364 NULL,
6365 ar,
6366 replmd_replicated_apply_search_callback,
6374 }
6377 }
6379 /*
6380 * This is essentially a wrapper for replmd_replicated_apply_next()
6381 *
6382 * This is needed to ensure that both codepaths call this handler.
6383 */
6385 {
6390 if (ar->isDeleted && (ret != LDB_SUCCESS || ldb_dn_compare(msg->dn, deleted_objects_dn) != 0)) {
6391 /*
6392 * Do a delete here again, so that if there is
6393 * anything local that conflicts with this
6394 * object being deleted, it is removed. This
6395 * includes links. See MS-DRSR 4.1.10.6.9
6396 * UpdateObject.
6397 *
6398 * If the object is already deleted, and there
6399 * is no more work required, it doesn't do
6400 * anything.
6401 */
6403 /* This has been updated to point to the DN we eventually did the modify on */
6412 }
6419 }
6421 /* Build a delete request, which hopefully will artually turn into nothing */
6424 NULL,
6425 res,
6426 ldb_modify_default_callback,
6432 }
6434 /*
6435 * This is the guts of the call, call back
6436 * into our delete code, but setting the
6437 * re_delete flag so we delete anything that
6438 * shouldn't be there on a deleted or recycled
6439 * object
6440 */
6444 }
6449 }
6450 }
6454 }
6458 {
6466 LDB_ERR_OPERATIONS_ERROR);
6467 }
6471 }
6476 LDB_ERR_OPERATIONS_ERROR);
6477 }
6482 }
6485 {
6504 NTTIME now;
6518 /* this happens for a REPL_OBJ call where we are
6519 creating the target object by replicating it. The
6520 subdomain join code does this for the partition DN
6521 */
6524 }
6531 }
6533 /*
6534 * first create the new replUpToDateVector
6535 */
6543 }
6547 }
6548 }
6550 /*
6551 * the new uptodateness vector will at least
6552 * contain 1 entry, one for the source_dsa
6553 *
6554 * plus optional values from our old vector and the one from the source_dsa
6555 */
6561 if (!nuv.ctr.ctr2.cursors) return replmd_replicated_request_werror(ar, WERR_NOT_ENOUGH_MEMORY);
6563 /* first copy the old vector */
6566 ni++;
6567 }
6569 /* merge in the source_dsa vector is available */
6576 }
6582 }
6588 }
6590 }
6594 /* if it's not there yet, add it */
6596 ni++;
6597 }
6599 /*
6600 * finally correct the size of the cursors array
6601 */
6604 /*
6605 * sort the cursors
6606 */
6609 /*
6610 * create the change ldb_message
6611 */
6621 }
6625 }
6628 /*
6629 * now create the new repsFrom value from the given repsFromTo1 structure
6630 */
6638 /*
6639 * first see if we already have a repsFrom value for the current source dsa
6640 * if so we'll later replace this value
6641 */
6655 }
6659 }
6661 /*
6662 * we compare the source dsa objectGUID not the invocation_id
6663 * because we want only one repsFrom value per source dsa
6664 * and when the invocation_id of the source dsa has changed we don't need
6665 * the old repsFrom with the old invocation_id
6666 */
6671 }
6676 }
6678 /*
6679 * copy over all old values to the new ldb_message
6680 */
6684 }
6686 /*
6687 * if we haven't found an old repsFrom value for the current source dsa
6688 * we'll add a new value
6689 */
6697 }
6699 /* we now fill the value which is already attached to ldb_message */
6706 }
6708 /*
6709 * the ldb_message_element for the attribute, has all the old values and the new one
6710 * so we'll replace the whole attribute with all values
6711 */
6716 LDB_CHANGETYPE_MODIFY,
6717 msg);
6720 }
6722 /* prepare the ldb_modify() request */
6724 ldb,
6725 ar,
6726 msg,
6728 ar,
6729 replmd_replicated_uptodate_modify_callback,
6735 }
6739 {
6746 LDB_ERR_OPERATIONS_ERROR);
6747 }
6752 }
6760 /* we ignore referrals */
6767 }
6768 }
6772 }
6776 {
6786 NULL
6787 };
6792 /*
6793 * Let the caller know that we did an originating updates
6794 */
6798 ldb,
6799 ar,
6801 LDB_SCOPE_BASE,
6803 attrs,
6804 NULL,
6805 ar,
6806 replmd_replicated_uptodate_search_callback,
6812 }
6816 static int replmd_extended_replicated_objects(struct ldb_module *module, struct ldb_request *req)
6817 {
6830 ldb_debug(ldb, LDB_DEBUG_FATAL, "replmd_extended_replicated_objects: invalid extended data\n");
6832 }
6835 ldb_debug(ldb, LDB_DEBUG_FATAL, "replmd_extended_replicated_objects: extended data invalid version [%u != %u]\n",
6838 }
6844 /* Set the flags to have the replmd_op_callback run over the full set of objects */
6853 }
6861 }
6866 }
6868 /* If this change contained linked attributes in the body
6869 * (rather than in the links section) we need to update
6870 * backlinks in linked_attributes */
6874 }
6880 }
6882 /**
6883 * Checks how to handle an missing target - either we need to fail the
6884 * replication and retry with GET_TGT, ignore the link and continue, or try to
6885 * add a partial link to an unknown target.
6886 */
6896 {
6900 /*
6901 * we may not be able to resolve link targets properly when
6902 * dealing with subsets of objects, e.g. the source is a
6903 * critical object and the target isn't
6904 *
6905 * TODO:
6906 * When we implement Trusted Domains we need to consider
6907 * whether they get treated as an incomplete replica here or not
6908 */
6911 /*
6912 * Ignore the link. We don't increase the highwater-mark in
6913 * the object subset cases, so subsequent replications should
6914 * resolve any missing links
6915 */
6921 }
6925 /*
6926 * target should already be up-to-date so there's no point in
6927 * retrying. This could be due to bad timing, or if a target
6928 * on a one-way link was deleted. We ignore the link rather
6929 * than failing the replication cycle completely
6930 */
6936 }
6939 mem_ctx,
6940 source_dn,
6941 target_dn);
6943 /* fail the replication and retry with GET_TGT */
6945 missing_str,
6950 }
6952 /*
6953 * The target of the cross-partition link is missing. Continue
6954 * and try to at least add the forward-link. This isn't great,
6955 * but a partial link can be fixed by dbcheck, so it's better
6956 * than dropping the link completely.
6957 */
6962 /*
6963 * Only log this when we're actually committing the objects.
6964 * This avoids spurious logs, i.e. if we're just verifying the
6965 * received link during a join.
6966 */
6970 }
6973 }
6975 /**
6976 * Checks that the target object for a linked attribute exists.
6977 * @param guid returns the target object's GUID (is returned)if it exists)
6978 * @param ignore_link set to true if the linked attribute should be ignored
6979 * (i.e. the target doesn't exist, but that it's OK to skip the link)
6980 */
6988 {
6994 NTSTATUS ntstatus;
7004 /*
7005 * This strange behaviour (allowing a NULL/missing
7006 * GUID) originally comes from:
7007 *
7008 * commit e3054ce0fe0f8f62d2f5b2a77893e7a1479128bd
7009 * Author: Andrew Tridgell <tridge@samba.org>
7010 * Date: Mon Dec 21 21:21:55 2009 +1100
7011 *
7012 * s4-drs: cope better with NULL GUIDS from DRS
7013 *
7014 * It is valid to get a NULL GUID over DRS for a deleted forward link. We
7015 * need to match by DN if possible when seeing if we should update an
7016 * existing link.
7017 *
7018 * Pair-Programmed-With: Andrew Bartlett <abartlet@samba.org>
7019 */
7022 DSDB_FLAG_NEXT_MODULE |
7023 DSDB_SEARCH_SHOW_RECYCLED |
7024 DSDB_SEARCH_SEARCH_ALL_PARTITIONS |
7025 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT,
7026 NULL);
7028 ldb_asprintf_errstring(ldb, "Failed to find GUID in linked attribute 0x%x blob for %s from %s",
7037 attrs,
7038 DSDB_FLAG_NEXT_MODULE |
7039 DSDB_SEARCH_SHOW_RECYCLED |
7040 DSDB_SEARCH_SEARCH_ALL_PARTITIONS |
7041 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT,
7042 NULL,
7045 }
7053 }
7057 /*
7058 * target object is unknown. Check whether to ignore the link,
7059 * fail the replication, or add a partial link
7060 */
7075 /* Get the object's state (i.e. Not Deleted, Tombstone, etc) */
7079 /*
7080 * Check for deleted objects as per MS-DRSR 4.1.10.6.14
7081 * ProcessLinkValue(). Link updates should not be sent for
7082 * recycled and tombstone objects (deleting the links should
7083 * happen when we delete the object). This probably means our
7084 * copy of the target object isn't up to date.
7085 */
7088 /*
7089 * target object is deleted. Check whether to ignore the
7090 * link, fail the replication, or add a partial link
7091 */
7097 }
7098 }
7102 }
7104 /**
7105 * Extracts the key details about the source/target object for a
7106 * linked-attribute entry.
7107 * This returns the following details:
7108 * @param ret_attr the schema details for the linked attribute
7109 * @param source_msg the search result for the source object
7110 * @param target_dsdb_dn the unpacked DN info for the target object
7111 */
7118 {
7124 WERROR status;
7128 /*
7129 linked_attributes[0]:
7130 &objs->linked_attributes[i]: struct drsuapi_DsReplicaLinkedAttribute
7131 identifier : *
7132 identifier: struct drsuapi_DsReplicaObjectIdentifier
7133 __ndr_size : 0x0000003a (58)
7134 __ndr_size_sid : 0x00000000 (0)
7135 guid : 8e95b6a9-13dd-4158-89db-3220a5be5cc7
7136 sid : S-0-0
7137 __ndr_size_dn : 0x00000000 (0)
7138 dn : ''
7139 attid : DRSUAPI_ATTID_member (0x1F)
7140 value: struct drsuapi_DsAttributeValue
7141 __ndr_size : 0x0000007e (126)
7142 blob : *
7143 blob : DATA_BLOB length=126
7144 flags : 0x00000001 (1)
7145 1: DRSUAPI_DS_LINKED_ATTRIBUTE_FLAG_ACTIVE
7146 originating_add_time : Wed Sep 2 22:20:01 2009 EST
7147 meta_data: struct drsuapi_DsReplicaMetaData
7148 version : 0x00000015 (21)
7149 originating_change_time : Wed Sep 2 23:39:07 2009 EST
7150 originating_invocation_id: 794640f3-18cf-40ee-a211-a93992b67a64
7151 originating_usn : 0x000000000001e19c (123292)
7153 (for cases where the link is to a normal DN)
7154 &target: struct drsuapi_DsReplicaObjectIdentifier3
7155 __ndr_size : 0x0000007e (126)
7156 __ndr_size_sid : 0x0000001c (28)
7157 guid : 7639e594-db75-4086-b0d4-67890ae46031
7158 sid : S-1-5-21-2848215498-2472035911-1947525656-19924
7159 __ndr_size_dn : 0x00000022 (34)
7160 dn : 'CN=UOne,OU=TestOU,DC=vsofs8,DC=com'
7161 */
7163 /* find the attribute being modified */
7172 }
7179 /*
7180 * get the existing message from the db for the object with
7181 * this GUID, returning attribute being modified. We will then
7182 * use this msg as the basis for a modify call
7183 */
7185 DSDB_FLAG_NEXT_MODULE |
7186 DSDB_SEARCH_SEARCH_ALL_PARTITIONS |
7187 DSDB_SEARCH_SHOW_RECYCLED |
7188 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT |
7189 DSDB_SEARCH_REVEAL_INTERNALS,
7190 NULL,
7194 }
7199 }
7203 /* the value blob for the attribute holds the target object DN */
7211 }
7216 }
7218 /**
7219 * Verifies the source and target objects are known for a linked attribute
7220 */
7223 {
7236 /*
7237 * When we fail to find the source object, the error code we pass
7238 * back here is really important. It flags back to the callers to
7239 * retry this request with DRSUAPI_DRS_GET_ANC. This case should
7240 * never happen if we're replicating from a Samba DC, but it is
7241 * needed to talk to a Windows DC
7242 */
7245 }
7250 }
7252 /*
7253 * We can skip the target object checks if we're only syncing critical
7254 * objects, or we know the target is up-to-date. If either case, we
7255 * still continue even if the target doesn't exist
7256 */
7263 }
7265 /*
7266 * When we fail to find the target object, the error code we pass
7267 * back here is really important. It flags back to the callers to
7268 * retry this request with DRSUAPI_DRS_GET_TGT
7269 */
7272 }
7276 }
7278 /**
7279 * Finds the current active Parsed-DN value for a single-valued linked
7280 * attribute, if one exists.
7281 * @param ret_pdn assigned the active Parsed-DN, or NULL if none was found
7282 * @returns LDB_SUCCESS (regardless of whether a match was found), unless
7283 * an error occurred
7284 */
7291 {
7298 /* nothing to do for multi-valued linked attributes */
7300 }
7306 /* skip any inactive links */
7309 }
7311 /* we've found an active value for this attribute */
7319 }
7322 }
7324 /* no active link found */
7326 }
7328 /**
7329 * @returns true if the replication linked attribute info is newer than we
7330 * already have in our DB
7331 * @param pdn the existing linked attribute info in our DB
7332 * @param la the new linked attribute info received during replication
7333 */
7336 {
7337 /* see if this update is newer than what we have already */
7344 /* no existing info so update is newer */
7346 }
7354 version,
7356 change_time,
7358 }
7360 /**
7361 * Marks an existing linked attribute value as deleted in the DB
7362 * @param pdn the parsed-DN of the target-value to delete
7363 */
7375 {
7378 NTTIME now;
7388 }
7390 /* if the existing link is active, remove its backlink */
7398 }
7399 }
7401 /* mark the existing value as deleted */
7406 }
7408 /**
7409 * Checks for a conflict in single-valued link attributes, and tries to
7410 * resolve the problem if possible.
7411 *
7412 * Single-valued links should only ever have one active value. If we already
7413 * have an active link value, and during replication we receive an active link
7414 * value for a different target DN, then we need to resolve this inconsistency
7415 * and determine which value should be active. If the received info is better/
7416 * newer than the existing link attribute, then we need to set our existing
7417 * link as deleted. If the received info is worse/older, then we should continue
7418 * to add it, but set it as an inactive link.
7419 *
7420 * Note that this is a corner-case that is unlikely to happen (but if it does
7421 * happen, we don't want it to break replication completely).
7422 *
7423 * @param pdn_being_modified the parsed DN corresponding to the received link
7424 * target (note this is NULL if the link does not already exist in our DB)
7425 * @param pdn_list all the source object's Parsed-DNs for this attribute, i.e.
7426 * any existing active or inactive values for the attribute in our DB.
7427 * @param dsdb_dn the target DN for the received link attribute
7428 * @param add_as_inactive gets set to true if the received link is worse than
7429 * the existing link - it should still be added, but as an inactive link.
7430 */
7444 {
7449 /*
7450 * check if there's a conflict for single-valued links, i.e. an active
7451 * linked attribute already exists, but it has a different target value
7452 */
7459 }
7461 /*
7462 * If no active value exists (or the received info is for the currently
7463 * active value), then no conflict exists
7464 */
7467 }
7472 /* Work out how to resolve the conflict based on which info is better */
7480 /*
7481 * Delete our existing active link. The received info will then
7482 * be added (through normal link processing) as the active value
7483 */
7492 }
7498 /*
7499 * we want to keep our existing active link and add the
7500 * received link as inactive
7501 */
7503 }
7506 }
7508 /*
7509 process one linked attribute structure
7510 */
7515 {
7536 /*
7537 * get the attribute being modified, the search result for the source object,
7538 * and the target object's DN details
7539 */
7546 }
7548 /*
7549 * Check for deleted objects per MS-DRSR 4.1.10.6.14
7550 * ProcessLinkValue, because link updates are not applied to
7551 * recycled and tombstone objects. We don't have to delete
7552 * any existing link, that should have happened when the
7553 * object deletion was replicated or initiated.
7554 */
7560 }
7569 }
7572 }
7574 /* parse the existing links */
7581 }
7589 }
7591 /*
7592 * there are some cases where the target object doesn't exist, but it's
7593 * OK to ignore the linked attribute
7594 */
7598 }
7600 /* see if this link already exists */
7611 }
7619 }
7621 /* get a seq_num for this change */
7626 }
7628 /*
7629 * check for single-valued link conflicts, i.e. an active linked
7630 * attribute already exists, but it has a different target value
7631 */
7637 seq_num,
7642 }
7643 }
7649 /* remove the existing backlink */
7651 schema,
7654 parent);
7658 }
7659 }
7667 /*
7668 * We know where the new one needs to be, from the *next
7669 * pointer into pdn_list.
7670 */
7679 }
7680 }
7685 }
7686 }
7693 }
7698 }
7704 }
7706 /* set the link attribute's value to the info that was received */
7716 }
7720 /* Set the new link as inactive/deleted to avoid conflicts */
7724 val_to_update);
7729 }
7733 /* if the new link is active, then add the new backlink */
7735 schema,
7738 parent);
7742 }
7743 }
7745 /* we only change whenChanged and uSNChanged if the seq_num
7746 has changed */
7752 }
7759 }
7765 }
7771 }
7780 tmp_ctx,
7781 LDB_CHANGETYPE_MODIFY,
7782 msg));
7785 }
7790 }
7793 {
7796 }
7799 }
7802 /*
7803 we hook into the transaction operations to allow us to
7804 perform the linked attribute updates at the end of the whole
7805 transaction. This allows a forward linked attribute to be created
7806 before the object is created. During a vampire, w2k8 sends us linked
7807 attributes before the objects they are part of.
7808 */
7810 {
7811 /* create our private structure for this transaction */
7816 /* free any leftover mod_usn records from cancelled
7817 transactions */
7822 }
7827 }
7829 /*
7830 on prepare commit we loop over our queued la_context structures and
7831 apply each of them
7832 */
7834 {
7840 /*
7841 * Walk the list of linked attributes from DRS replication.
7842 *
7843 * We walk backwards, to do the first entry first, as we
7844 * added the entries with DLIST_ADD() which puts them at the
7845 * start of the list
7846 */
7855 }
7856 }
7860 /* possibly change @REPLCHANGED */
7864 }
7867 }
7870 {
7876 }
7890 };
7893 {
7896 }