| blob | 3ce69e06920e4dbfbca7af95b424a8d71ea1d729 |
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 */
2047 dn_str);
2052 }
2054 }
2058 }
2061 }
2066 }
2067 }
2068 /* keep a pointer to the original ldb_val */
2070 }
2073 }
2075 }
2077 /*
2078 * Get a series of trusted message element values. The result is sorted by
2079 * GUID, even though the GUIDs might not be known. That works because we trust
2080 * the database to give us the elements like that if the
2081 * replmd_private->sorted_links flag is set.
2082 *
2083 * We also ensure that the links are in the Functional Level 2003
2084 * linked attributes format.
2085 */
2093 {
2099 }
2102 /* We need to sort the list. This is the slow old path we want
2103 to avoid.
2104 */
2106 parent);
2109 }
2111 /* Here we get a list of 'struct parsed_dns' without the parsing */
2117 }
2121 }
2122 }
2124 /*
2125 * This upgrades links to FL2003 style, and sorts the result
2126 * if that was needed.
2127 *
2128 * TODO: Add a database feature that asserts we have no FL2000
2129 * style links to avoid this check or add a feature that
2130 * uses a similar check to find sorted/unsorted links
2131 * for an on-the-fly upgrade.
2132 */
2136 el,
2137 ldap_oid);
2140 }
2143 }
2145 /*
2146 Return LDB_SUCCESS if a parsed_dn list contains no duplicate values,
2147 otherwise an error code. For compatibility the error code differs depending
2148 on whether or not the attribute is "member".
2150 As always, the parsed_dn list is assumed to be sorted.
2151 */
2155 {
2163 "Linked attribute %s has "
2170 }
2171 }
2172 }
2174 }
2176 /*
2177 build a new extended DN, including all meta data fields
2179 RMD_FLAGS = DSDB_RMD_FLAG_* bits
2180 RMD_ADDTIME = originating_add_time
2181 RMD_INVOCID = originating_invocation_id
2182 RMD_CHANGETIME = originating_change_time
2183 RMD_ORIGINATING_USN = originating_usn
2184 RMD_LOCAL_USN = local_usn
2185 RMD_VERSION = version
2186 */
2191 {
2195 }
2197 static int replmd_update_la_val(TALLOC_CTX *mem_ctx, struct ldb_val *v, struct dsdb_dn *dsdb_dn,
2202 /*
2203 check if any links need upgrading from w2k format
2204 */
2209 {
2213 NTSTATUS status;
2218 ldap_oid);
2221 }
2222 }
2227 /*
2228 * We optimistically assume they are all the same; if
2229 * the first one is fixed, they are all fixed.
2230 *
2231 * If the first one was *not* fixed and we find a
2232 * later one that is, that is an occasion to shout
2233 * with DEBUG(0).
2234 */
2237 }
2241 }
2247 }
2248 }
2251 /* it's an old one that needs upgrading */
2257 }
2258 }
2260 /*
2261 * This sort() is critical for the operation of
2262 * get_parsed_dns_trusted() because callers of this function
2263 * expect a sorted list, and FL2000 style links are not
2264 * sorted. In particular, as well as the upgrade case,
2265 * get_parsed_dns_trusted() is called from
2266 * replmd_delete_remove_link() even in FL2000 mode
2267 *
2268 * We do not normally pay the cost of the qsort() due to the
2269 * early return in the RMD_VERSION found case.
2270 */
2273 }
2275 /*
2276 Sets the value for a linked attribute, including all meta data fields
2278 see replmd_build_la_val for value names
2279 */
2284 {
2292 NTSTATUS status;
2301 }
2307 }
2313 }
2319 }
2324 }
2330 /* get the ADDTIME from the original */
2334 }
2337 }
2342 }
2344 /* use our invocation id */
2348 /* changetime is the current time */
2352 /* update the USN */
2367 }
2371 }
2373 /**
2374 * Updates the value for a linked attribute, including all meta data fields
2375 */
2376 static int replmd_update_la_val(TALLOC_CTX *mem_ctx, struct ldb_val *v, struct dsdb_dn *dsdb_dn,
2380 {
2383 NTSTATUS status;
2385 /*
2386 * We're updating the linked attribute locally, so increase the version
2387 * by 1 so that other DCs will see the change when it gets replicated out
2388 */
2394 }
2398 }
2400 /*
2401 handle adding a linked attribute
2402 */
2413 {
2423 NTTIME now;
2426 /* get the DNs to be added, fully parsed.
2427 *
2428 * We need full parsing because they came off the wire and we don't
2429 * trust them, besides which we need their details to know where to put
2430 * them.
2431 */
2437 }
2439 /* get the existing DNs, lazily parsed */
2447 }
2456 }
2464 }
2466 /*
2467 * For each new value, find where it would go in the list. If there is
2468 * a matching GUID there, we update the existing value; otherwise we
2469 * put it in place.
2470 */
2486 }
2489 /*
2490 * We are trying to add one that exists, which is only
2491 * allowed if it was previously deleted.
2492 *
2493 * When we do undelete a link we change it in place.
2494 * It will be copied across into the right spot in due
2495 * course.
2496 */
2503 "Attribute %s already "
2509 /* error codes for 'member' need to be
2510 special cased */
2515 }
2516 }
2527 }
2531 msg_dn,
2534 schema_attr,
2535 parent);
2539 }
2541 }
2542 /*
2543 * Here we don't have an exact match.
2544 *
2545 * If next is NULL, this one goes beyond the end of the
2546 * existing list, so we need to add all of those ones first.
2547 *
2548 * If next is not NULL, we need to add all the ones before
2549 * next.
2550 */
2554 /* next should have been parsed, but let's make sure */
2560 }
2561 }
2563 }
2565 /* put all the old ones before next on the list */
2568 num_values++;
2569 }
2575 parent);
2576 /* Make the new linked attribute ldb_val. */
2583 }
2584 num_values++;
2588 }
2589 }
2590 /* copy the rest of the old ones (if any) */
2593 num_values++;
2594 }
2599 }
2605 /* we now tell the backend to replace all existing values
2606 with the one we have constructed */
2610 }
2613 /*
2614 handle deleting all active linked attributes
2615 */
2626 {
2636 NTTIME now;
2641 /* there is nothing to delete... */
2643 /* and we're deleting nothing, so that's OK */
2645 }
2647 }
2652 }
2659 }
2668 }
2675 }
2676 }
2678 /* we empty out el->values here to avoid damage if we return early. */
2682 /*
2683 * If vanish links is set, we are actually removing members of
2684 * old_el->values; otherwise we are just marking them deleted.
2685 *
2686 * There is a special case when no values are given: we remove them
2687 * all. When we have the vanish_links control we just have to remove
2688 * the backlinks and change our element to replace the existing values
2689 * with the empty list.
2690 */
2700 }
2701 }
2705 parent);
2709 }
2712 }
2717 }
2727 }
2728 }
2734 }
2735 }
2744 NULL,
2752 }
2765 }
2766 }
2776 "attribute %s to %s, because "
2779 }
2780 }
2782 /* remove the backlink */
2784 replmd_private,
2786 msg_dn,
2789 parent);
2793 }
2795 /* We flag the deletion and tidy it up later. */
2798 }
2814 }
2815 }
2825 }
2830 parent);
2834 }
2835 }
2846 }
2850 }
2852 j++;
2853 }
2856 }
2858 }
2865 /* we now tell the backend to replace all existing values
2866 with the one we have constructed */
2870 }
2872 /*
2873 handle replacing a linked attribute
2874 */
2886 {
2898 NTTIME now;
2905 }
2907 /*
2908 * The replace operation is unlike the replace and delete cases in that
2909 * we need to look at every existing link to see whether it is being
2910 * retained or deleted. In other words, we can't avoid parsing the GUIDs.
2911 *
2912 * As we are trying to combine two sorted lists, the algorithm we use
2913 * is akin to the merge phase of a merge sort. We interleave the two
2914 * lists, doing different things depending on which side the current
2915 * item came from.
2916 *
2917 * There are three main cases, with some sub-cases.
2918 *
2919 * - a DN is in the old list but not the new one. It needs to be
2920 * marked as deleted (but left in the list).
2921 * - maybe it is already deleted, and we have less to do.
2922 *
2923 * - a DN is in both lists. The old data gets replaced by the new,
2924 * and the list doesn't grow. The old link may have been marked as
2925 * deleted, in which case we undelete it.
2926 *
2927 * - a DN is in the new list only. We add it in the right place.
2928 */
2935 /* There is nothing to do! */
2937 }
2943 }
2949 }
2956 }
2963 }
2970 }
2982 /* the new list is empty, read the old list */
2987 /* the old list is empty, read new list */
2993 }
2996 /*
2997 * An old ones that come before the next replacement
2998 * (if any). We mark it as deleted and add it to the
2999 * final list.
3000 */
3006 invocation_id,
3012 }
3015 schema,
3016 msg_dn,
3018 schema_attr,
3019 parent);
3023 }
3024 }
3026 old_i++;
3028 /*
3029 * We are overwriting one. If it was previously
3030 * deleted, we need to add a backlink.
3031 *
3032 * Note that if any RMD_FLAGs in an extended new DN
3033 * will be ignored.
3034 */
3040 invocation_id,
3046 }
3051 schema,
3052 msg_dn,
3054 schema_attr,
3055 parent);
3059 }
3060 }
3063 old_i++;
3064 new_i++;
3066 /*
3067 * Replacements that don't match an existing one. We
3068 * just add them to the final list.
3069 */
3073 invocation_id,
3078 }
3080 schema,
3081 msg_dn,
3083 schema_attr,
3084 parent);
3088 }
3090 new_i++;
3091 }
3092 }
3095 }
3103 }
3106 /*
3107 handle linked attributes in modify requests
3108 */
3115 {
3123 /*
3124 * Nothing special is required for modifying or vanishing links
3125 * in fl2000 since they are just strings in a multi-valued
3126 * attribute.
3127 */
3129 DSDB_CONTROL_REPLMD_VANISH_LINKS);
3132 }
3134 }
3136 /*
3137 * TODO:
3138 *
3139 * We should restrict this to the intersection of the list of
3140 * linked attributes in the schema and the list of attributes
3141 * being modified.
3142 *
3143 * This will help performance a little, as otherwise we have
3144 * to allocate the entire object value-by-value.
3145 */
3147 DSDB_FLAG_NEXT_MODULE |
3148 DSDB_SEARCH_SHOW_RECYCLED |
3149 DSDB_SEARCH_REVEAL_INTERNALS |
3150 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT,
3151 parent);
3154 }
3169 }
3172 }
3178 DSDB_CONTROL_REPLMD_VANISH_LINKS);
3182 }
3184 DSDB_CONTROL_DBCHECK);
3187 }
3188 }
3190 /* Odd is for the target. Illegal to modify */
3194 }
3202 parent);
3209 parent);
3216 parent);
3223 }
3228 /* Return codes as found on Windows 2012r2 */
3233 }
3236 }
3240 }
3243 }
3248 /* TODO: this relises a bit too heavily on the exact
3249 behaviour of ldb_msg_find_element and
3250 ldb_msg_remove_element */
3254 i--;
3255 }
3256 }
3260 }
3266 {
3272 WERROR werr;
3285 server_dn);
3286 }
3287 }
3291 }
3294 domain,
3299 }
3302 }
3306 {
3323 /* do not manipulate our control entries */
3326 }
3329 DSDB_CONTROL_SEC_DESC_PROPAGATION_OID);
3333 }
3338 }
3341 }
3346 DSDB_CONTROL_DBCHECK_FIX_DUPLICATE_LINKS);
3353 }
3357 }
3362 }
3368 }
3372 }
3376 }
3379 DSDB_CONTROL_DBCHECK_FIX_LINK_DN_NAME);
3386 }
3390 }
3394 }
3398 }
3402 }
3407 }
3412 }
3418 }
3422 }
3426 }
3428 /*
3429 * If we are run from dbcheck and we are not updating
3430 * a link (as these would need to be sorted and so
3431 * can't go via such a simple update, then do not
3432 * trigger replicated updates and a new USN from this
3433 * change, it wasn't a real change, just a new
3434 * (correct) string DN
3435 */
3439 }
3448 }
3453 }
3457 /* we have to copy the message as the caller might have it as a const */
3463 }
3478 }
3483 }
3490 }
3492 /* TODO:
3493 * - replace the old object with the newly constructed one
3494 */
3499 msg,
3502 req);
3507 }
3509 /* current partition control is needed by "replmd_op_callback" */
3512 DSDB_CONTROL_CURRENT_PARTITION_OID,
3517 }
3518 }
3520 /* If we are in functional level 2000, then
3521 * replmd_modify_handle_linked_attribs will have done
3522 * nothing */
3528 }
3529 }
3533 /* we only change whenChanged and uSNChanged if the seq_num
3534 has changed */
3541 }
3548 }
3549 }
3551 /* go on with the call chain */
3553 }
3557 /*
3558 handle a rename request
3560 On a rename we need to do an extra ldb_modify which sets the
3561 whenChanged and uSNChanged attributes. We do this in a callback after the success.
3562 */
3564 {
3570 /* do not manipulate our control entries */
3573 }
3582 }
3594 }
3596 /* go on with the call chain */
3598 }
3600 /* After the rename is compleated, update the whenchanged etc */
3602 {
3625 }
3632 LDB_ERR_OPERATIONS_ERROR);
3633 }
3635 /* TODO:
3636 * - replace the old object with the newly constructed one
3637 */
3643 }
3654 }
3656 /* normalize the rdn attribute name */
3662 }
3670 }
3676 }
3681 }
3686 }
3691 }
3693 /*
3694 * here we let replmd_update_rpmd() only search for
3695 * the existing "replPropertyMetaData" and rdn_name attributes.
3696 *
3697 * We do not want the existing "name" attribute as
3698 * the "name" attribute needs to get the version
3699 * updated on rename even if the rdn value hasn't changed.
3700 *
3701 * This is the diff of the meta data, for a moved user
3702 * on a w2k8r2 server:
3703 *
3704 * # record 1
3705 * -dn: CN=sdf df,CN=Users,DC=bla,DC=base
3706 * +dn: CN=sdf df,OU=TestOU,DC=bla,DC=base
3707 * replPropertyMetaData: NDR: struct replPropertyMetaDataBlob
3708 * version : 0x00000001 (1)
3709 * reserved : 0x00000000 (0)
3710 * @@ -66,11 +66,11 @@ replPropertyMetaData: NDR: struct re
3711 * local_usn : 0x00000000000037a5 (14245)
3712 * array: struct replPropertyMetaData1
3713 * attid : DRSUAPI_ATTID_name (0x90001)
3714 * - version : 0x00000001 (1)
3715 * - originating_change_time : Wed Feb 9 17:20:49 2011 CET
3716 * + version : 0x00000002 (2)
3717 * + originating_change_time : Wed Apr 6 15:21:01 2011 CEST
3718 * originating_invocation_id: 0d36ca05-5507-4e62-aca3-354bab0d39e1
3719 * - originating_usn : 0x00000000000037a5 (14245)
3720 * - local_usn : 0x00000000000037a5 (14245)
3721 * + originating_usn : 0x0000000000003834 (14388)
3722 * + local_usn : 0x0000000000003834 (14388)
3723 * array: struct replPropertyMetaData1
3724 * attid : DRSUAPI_ATTID_userAccountControl (0x90008)
3725 * version : 0x00000004 (4)
3726 */
3740 }
3745 }
3752 }
3756 msg,
3759 req);
3764 }
3766 /* current partition control is needed by "replmd_op_callback" */
3769 DSDB_CONTROL_CURRENT_PARTITION_OID,
3774 }
3775 }
3784 }
3791 }
3793 /* go on with the call chain - do the modify after the rename */
3795 }
3797 /*
3798 * remove links from objects that point at this object when an object
3799 * is deleted. We remove it from the NEXT module per MS-DRSR 5.160
3800 * RemoveObj which states that link removal due to the object being
3801 * deleted is NOT an originating update - they just go away!
3802 *
3803 */
3812 {
3835 }
3841 }
3843 /* remove the link */
3849 }
3857 }
3866 }
3870 DSDB_FLAG_NEXT_MODULE |
3871 DSDB_SEARCH_SHOW_EXTENDED_DN |
3872 DSDB_SEARCH_SHOW_RECYCLED,
3873 parent);
3878 }
3886 }
3888 /*
3889 * This call 'upgrades' the links in link_dns, but we
3890 * do not commit the result back into the database, so
3891 * this is safe to call in FL2000 or on databases that
3892 * have been run at that level in the past.
3893 */
3900 }
3910 }
3914 "Failed to find forward link on %s "
3922 }
3925 /* This needs to get the Binary DN, by first searching */
3933 /*
3934 * Ensure that we tell the modification to vanish any linked
3935 * attributes (not simply mark them as isDeleted = TRUE)
3936 */
3943 }
3944 }
3947 }
3950 /*
3951 handle update of replication meta data for deletion of objects
3953 This also handles the mapping of delete to a rename operation
3954 to allow deletes to be replicated.
3956 It also handles the incoming deleted objects, to ensure they are
3957 fully deleted here. In that case re_delete is true, and we do not
3958 use this as a signal to change the deleted state, just reinforce it.
3960 */
3961 static int replmd_delete_internals(struct ldb_module *module, struct ldb_request *req, bool re_delete)
3962 {
3976 /* yes, this really is a hard coded list. See MS-ADTS
3977 section 3.1.1.5.5.1.1 */
4019 NULL
4020 };
4022 DSDB_SECRET_ATTRIBUTES,
4024 NULL
4025 };
4029 };
4038 }
4040 /*
4041 * We have to allow dbcheck to remove an object that
4042 * is beyond repair, and to do so totally. This could
4043 * mean we we can get a partial object from the other
4044 * DC, causing havoc, so dbcheck suggests
4045 * re-replication first. dbcheck sets both DBCHECK
4046 * and RELAX in this situation.
4047 */
4050 /* really, really remove it */
4052 }
4058 }
4064 }
4068 /* we need the complete msg off disk, so we can work out which
4069 attributes need to be removed */
4071 DSDB_FLAG_NEXT_MODULE |
4072 DSDB_SEARCH_SHOW_RECYCLED |
4073 DSDB_SEARCH_REVEAL_INTERNALS |
4083 }
4090 /* This supports us noticing an incoming isDeleted and acting on it */
4094 }
4097 /*
4098 * We have to prevent objects being deleted, even if
4099 * the administrator really wants them gone, as
4100 * without the tombstone, we can get a partial object
4101 * from the other DC, causing havoc.
4102 *
4103 * The only other valid case is when the 180 day
4104 * timeout has expired, when relax is specified.
4105 */
4107 /* it is already deleted - really remove it this time */
4110 }
4116 }
4123 }
4130 }
4134 /* consider the SYSTEM_FLAG_DISALLOW_MOVE_ON_DELETE flag */
4135 disallow_move_on_delete =
4139 /* work out where we will be renaming this object to */
4145 /*
4146 * We should not move objects if we can't find the
4147 * deleted objects DN. Not moving (or otherwise
4148 * harming) the Deleted Objects DN itself is handled
4149 * in the caller.
4150 */
4157 }
4159 /* this is probably an attempted delete on a partition
4160 * that doesn't allow delete operations, such as the
4161 * schema partition */
4168 }
4175 }
4176 }
4178 /* get the objects GUID from the search we just did */
4185 ldb,
4186 new_dn,
4188 guid);
4193 }
4202 }
4205 /*
4206 * No matter what has happened with other renames etc, try again to
4207 * get this to be under the deleted DN. See MS-DRSR 5.160 RemoveObj
4208 */
4218 }
4229 }
4230 }
4232 /*
4233 now we need to modify the object in the following ways:
4235 - add isDeleted=TRUE
4236 - update rDN and name, with new rDN
4237 - remove linked attributes
4238 - remove objectCategory and sAMAccountType
4239 - remove attribs not on the preserved list
4240 - preserved if in above list, or is rDN
4241 - remove all linked attribs from this object
4242 - remove all links from other objects to this object
4243 - add lastKnownParent
4244 - update replPropertyMetaData?
4246 see MS-ADTS "Tombstone Requirements" section 3.1.1.5.5.1.1
4247 */
4254 /* we need the storage form of the parent GUID */
4257 DSDB_FLAG_NEXT_MODULE |
4258 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT |
4259 DSDB_SEARCH_REVEAL_INTERNALS|
4263 "repmd_delete: Failed to %s %s, "
4271 }
4273 /*
4274 * Now we can use the DB version,
4275 * it will have the extended DN info in it
4276 */
4279 parent_dn,
4284 }
4287 parent_dn_str);
4290 ": Failed to add lastKnownParent "
4295 }
4301 }
4308 ": Failed to add msDS-LastKnownRDN "
4313 }
4319 }
4321 }
4322 }
4329 /*
4330 * MS-ADTS 3.1.1.5.5.1.1 Tombstone Requirements
4331 * describes what must be removed from a tombstone
4332 * object
4333 *
4334 * MS-ADTS 3.1.1.5.5.1.3 Recycled-Object Requirements
4335 * describes what must be removed from a recycled
4336 * object
4337 *
4338 */
4340 /*
4341 * we also mark it as recycled, meaning this object can't be
4342 * recovered (we are stripping its attributes).
4343 * This is done only if we have this schema object of course ...
4344 * This behavior is identical to the one of Windows 2008R2 which
4345 * always set the isRecycled attribute, even if the recycle-bin is
4346 * not activated and what ever the forest level is.
4347 */
4358 }
4360 }
4364 /* work out which of the old attributes we will be removing */
4372 }
4374 /* don't remove the rDN */
4376 }
4379 /*
4380 we have a backlink in this object
4381 that needs to be removed. We're not
4382 allowed to remove it directly
4383 however, so we instead setup a
4384 modify to delete the corresponding
4385 forward link
4386 */
4388 replmd_private,
4392 /*
4393 * now we continue, which means we
4394 * won't remove this backlink
4395 * directly
4396 */
4398 }
4404 __location__
4405 ": Failed to remove backlink of "
4408 old_dn_str,
4412 }
4414 /*
4415 * Otherwise vanish the link, we are
4416 * out of sync and the controlling
4417 * object does not have the source
4418 * link any more
4419 */
4426 }
4429 }
4431 /*
4432 * Ensure that we tell the modification to vanish any linked
4433 * attributes (not simply mark them as isDeleted = TRUE)
4434 */
4436 }
4442 }
4443 }
4448 /*
4449 * MS-ADTS 3.1.1.5.5.1.2 Deleted-Object Requirements
4450 * describes what must be removed from a deleted
4451 * object
4452 */
4459 }
4466 }
4472 }
4477 /* work out what the new rdn value is, for updating the
4478 rDN and name fields */
4483 }
4489 }
4496 }
4505 }
4507 }
4508 }
4510 /*
4511 * TODO: Per MS-DRSR 5.160 RemoveObj we should remove links directly, not as an originating update!
4512 *
4513 */
4515 /*
4516 * No matter what has happned with other renames, try again to
4517 * get this to be under the deleted DN.
4518 */
4520 /* now rename onto the new DN */
4529 }
4531 }
4539 }
4544 }
4547 {
4549 }
4553 {
4555 }
4557 static int replmd_replicated_request_werror(struct replmd_replicated_request *ar, WERROR status)
4558 {
4560 /* TODO: do some error mapping */
4562 /* Let the caller know the full WERROR */
4566 }
4572 {
4579 }
4580 }
4582 }
4585 /*
4586 return true if an update is newer than an existing entry
4587 see section 5.11 of MS-ADTS
4588 */
4593 NTTIME current_change_time,
4594 NTTIME update_change_time)
4595 {
4598 }
4601 }
4603 }
4607 {
4614 }
4619 {
4622 /*
4623 * If the new replPropertyMetaData entry for this attribute is
4624 * not provided (this happens in the case where we look for
4625 * ATTID_name, but the name was not changed), then the local
4626 * state is clearly still current, as the remote
4627 * server didn't send it due to being older the high watermark
4628 * USN we sent.
4629 */
4632 }
4635 /*
4636 * if we compare equal then do an
4637 * update. This is used when a client
4638 * asks for a FULL_SYNC, and can be
4639 * used to recover a corrupt
4640 * replica.
4641 *
4642 * This call is a bit tricky, what we
4643 * are doing it turning the 'is_newer'
4644 * call into a 'not is older' by
4645 * swapping cur_m and new_m, and negating the
4646 * outcome.
4647 */
4649 cur_m);
4652 new_m);
4653 }
4655 }
4658 /*
4659 form a DN for a deleted (DEL:) or conflict (CNF:) DN
4660 */
4668 {
4682 }
4684 /*
4685 * TODO: Per MS-ADTS 3.1.1.5.5 Delete Operation
4686 * we should truncate this value to ensure the RDN is not more than 255 chars.
4687 *
4688 * However we MS-ADTS 3.1.1.5.1.2 Naming Constraints indicates that:
4689 *
4690 * "Naming constraints are not enforced for replicated
4691 * updates." so this is safe and we don't have to work out not
4692 * splitting a UTF8 char right now.
4693 */
4696 /*
4697 * sizeof(guid_str.buf) will always be longer than
4698 * strlen(guid_str.buf) but we allocate using this and
4699 * waste the trailing bytes to avoid scaring folks
4700 * with memcpy() using strlen() below
4701 */
4703 deleted_child_rdn_val.data
4713 }
4722 /*
4723 * talloc won't allocate more than 256MB so we can't
4724 * overflow but just to be sure
4725 */
4728 }
4737 /* Now set the value into the RDN, without parsing it */
4739 dn,
4741 rdn_name,
4742 deleted_child_rdn_val);
4745 }
4748 /*
4749 form a conflict DN
4750 */
4755 {
4765 }
4770 }
4775 rdn_name,
4776 rdn_val,
4780 }
4782 }
4784 /*
4785 form a deleted DN
4786 */
4793 {
4797 rdn_name,
4798 rdn_value,
4799 guid);
4800 }
4803 /*
4804 perform a modify operation which sets the rDN and name attributes to
4805 their current values. This has the effect of changing these
4806 attributes to have been last updated by the current DC. This is
4807 needed to ensure that renames performed as part of conflict
4808 resolution are propagated to other DCs
4809 */
4812 {
4822 }
4828 }
4830 /* normalize the rdn attribute name */
4834 }
4840 }
4844 }
4847 }
4850 }
4853 }
4855 /*
4856 * We have to mark this as a replicated update otherwise
4857 * schema_data may reject a rename in the schema partition
4858 */
4862 req);
4868 }
4874 failed:
4879 }
4882 /*
4883 callback for conflict DN handling where we have renamed the incoming
4884 record. After renaming it, we need to ensure the change of name and
4885 rDN for the incoming record is seen as an originating update by this DC.
4887 This also handles updating lastKnownParent for entries sent to lostAndFound
4888 */
4890 {
4897 /* call the normal callback for everything except success */
4899 }
4910 }
4912 /* perform a modify of the rDN and name of the record */
4917 }
4924 }
4929 ldb_dn_get_extended_linearized(msg, ar->objs->objects[ar->index_current].last_known_parent, 1));
4934 }
4943 }
4945 }
4948 }
4950 /*
4951 callback for replmd_replicated_apply_add()
4952 This copes with the creation of conflict records in the case where
4953 the DN exists, but with a different objectGUID
4954 */
4955 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))
4956 {
4971 /* call the normal callback for success */
4974 }
4976 /*
4977 * we have a conflict, and need to decide if we will keep the
4978 * new record or the old record
4979 */
4984 /* For failures other than conflicts, fail the whole operation here */
4986 ldb_asprintf_errstring(ldb_module_get_ctx(ar->module), "Failed to locally apply remote add of %s: %s",
4991 LDB_ERR_OPERATIONS_ERROR);
4992 }
4996 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)));
4998 LDB_ERR_OPERATIONS_ERROR);
5000 }
5003 /*
5004 * We are on an RODC, or were a GC for this
5005 * partition, so we have to fail this until
5006 * someone who owns the partition sorts it
5007 * out
5008 */
5010 "Conflict adding object '%s' from incoming replication as we are read only for the partition. \n"
5015 }
5017 /*
5018 * first we need the replPropertyMetaData attribute from the
5019 * local, conflicting record
5020 */
5022 attrs,
5023 DSDB_FLAG_NEXT_MODULE |
5024 DSDB_SEARCH_SHOW_DELETED |
5030 }
5037 }
5045 }
5049 /*
5050 * we decide which is newer based on the RPMD on the name
5051 * attribute. See [MS-DRSR] ResolveNameConflict.
5052 *
5053 * We expect omd_name to be present, as this is from a local
5054 * search, but while rmd_name should have been given to us by
5055 * the remote server, if it is missing we just prefer the
5056 * local name in
5057 * replmd_replPropertyMetaData1_new_should_be_taken()
5058 */
5062 DEBUG(0,(__location__ ": Failed to find name attribute in local LDB replPropertyMetaData for %s\n",
5065 }
5067 /*
5068 * Should we preserve the current record, and so rename the
5069 * incoming record to be a conflict?
5070 */
5071 rename_incoming_record
5072 = !replmd_replPropertyMetaData1_new_should_be_taken(ar->objs->dsdb_repl_flags & DSDB_REPL_FLAG_PRIORITISE_INCOMING,
5084 }
5092 }
5097 /* re-submit the request, but with the new DN */
5101 /* we are renaming the existing record */
5110 }
5119 }
5132 }
5134 /*
5135 * now we need to ensure that the rename is seen as an
5136 * originating update. We do that with a modify.
5137 */
5141 }
5143 DEBUG(2,(__location__ ": With conflicting record renamed, re-apply replicated creation of '%s'\n",
5145 }
5149 req,
5150 msg,
5152 ar,
5153 callback,
5154 req);
5157 }
5160 /* current partition control needed by "repmd_op_callback" */
5162 DSDB_CONTROL_CURRENT_PARTITION_OID,
5166 }
5169 /* this tells the partition module to make it a
5170 partial replica if creating an NC */
5172 DSDB_CONTROL_PARTIAL_REPLICA,
5176 }
5177 }
5179 /*
5180 * Finally we re-run the add, otherwise the new record won't
5181 * exist, as we are here because of that exact failure!
5182 */
5184 failed:
5186 /* on failure make the caller get the error. This means
5187 * replication will stop with an error, but there is not much
5188 * else we can do.
5189 */
5192 }
5194 ret);
5195 }
5197 /*
5198 callback for replmd_replicated_apply_add()
5199 This copes with the creation of conflict records in the case where
5200 the DN exists, but with a different objectGUID
5201 */
5203 {
5208 /* This is like a conflict DN, where we put the object in LostAndFound
5209 see MS-DRSR 4.1.10.6.10 FindBestParentObject */
5211 }
5214 }
5216 /*
5217 this is called when a new object comes in over DRS
5218 */
5220 {
5231 NTTIME now;
5247 }
5254 }
5256 ret = ldb_msg_add_string(msg, "whenChanged", ar->objs->objects[ar->index_current].when_changed);
5259 }
5264 }
5269 }
5271 /* remove any message elements that have zero values */
5281 }
5287 i--;
5289 }
5290 }
5296 LDB_CHANGETYPE_ADD,
5297 msg);
5300 s));
5307 }
5311 /*
5312 * the meta data array is already sorted by the caller, except
5313 * for the RDN, which needs to be added.
5314 */
5322 ldb_asprintf_errstring(ldb, "%s: error during DRS repl ADD: %s", __func__, ldb_errstring(ldb));
5324 }
5328 ldb_asprintf_errstring(ldb, "%s: error during DRS repl ADD: %s", __func__, ldb_errstring(ldb));
5330 }
5334 }
5340 }
5344 }
5354 }
5355 }
5360 ldb,
5361 ar,
5362 msg,
5364 ar,
5365 replmd_op_add_callback,
5370 /* current partition control needed by "repmd_op_callback" */
5372 DSDB_CONTROL_CURRENT_PARTITION_OID,
5377 /* this tells the partition module to make it a
5378 partial replica if creating an NC */
5380 DSDB_CONTROL_PARTIAL_REPLICA,
5383 }
5386 }
5390 {
5397 LDB_ERR_OPERATIONS_ERROR);
5398 }
5400 /*
5401 * The error NO_SUCH_OBJECT is not expected, unless the search
5402 * base is the partition DN, and that case doesn't happen here
5403 * because then we wouldn't get a parent_guid_value in any
5404 * case.
5405 */
5409 }
5413 {
5421 /* Per MS-DRSR 4.1.10.6.10
5422 * FindBestParentObject we need to move this
5423 * new object under a deleted object to
5424 * lost-and-found */
5430 "No suitable NC root found for %s. "
5431 "We need to move this object because parent object %s "
5438 "Unable to find NC root for %s: %s. "
5439 "We need to move this object because parent object %s "
5445 }
5448 nc_root,
5449 DS_GUID_LOSTANDFOUND_CONTAINER,
5453 "Unable to find LostAndFound Container for %s "
5454 "in partition %s: %s. "
5455 "We need to move this object because parent object %s "
5461 }
5466 parent_dn
5469 }
5477 }
5478 }
5482 }
5484 }
5486 /* we ignore referrals */
5503 }
5505 /*
5506 * This error code is really important, as it
5507 * is the flag back to the callers to retry
5508 * this with DRSUAPI_DRS_GET_ANC, and so get
5509 * the parent objects before the child
5510 * objects
5511 */
5514 }
5520 }
5523 }
5524 }
5528 }
5530 /*
5531 * Look for the parent object, so we put the new object in the right
5532 * place This is akin to NameObject in MS-DRSR - this routine and the
5533 * callbacks find the right parent name, and correct name for this
5534 * object
5535 */
5538 {
5554 }
5555 }
5564 ldb,
5565 ar,
5567 LDB_SCOPE_SUBTREE,
5568 filter,
5569 attrs,
5570 NULL,
5571 ar,
5572 replmd_replicated_apply_search_for_parent_callback,
5577 DSDB_SEARCH_SHOW_RECYCLED|
5578 DSDB_SEARCH_SHOW_DELETED|
5579 DSDB_SEARCH_SHOW_EXTENDED_DN);
5582 }
5585 }
5587 /*
5588 handle renames that come in over DRS replication
5589 */
5594 {
5619 }
5623 ldb_asprintf_errstring(ldb_module_get_ctx(ar->module), "Failed to locally apply remote rename from %s to %s: %s",
5628 }
5636 }
5637 /*
5638 * we have a conflict, and need to decide if we will keep the
5639 * new record or the old record
5640 */
5645 /*
5646 * We are on an RODC, or were a GC for this
5647 * partition, so we have to fail this until
5648 * someone who owns the partition sorts it
5649 * out
5650 */
5652 "Conflict adding object '%s' from incoming replication but we are read only for the partition. \n"
5657 }
5659 /*
5660 * first we need the replPropertyMetaData attribute from the
5661 * old record
5662 */
5664 attrs,
5665 DSDB_FLAG_NEXT_MODULE |
5666 DSDB_SEARCH_SHOW_DELETED |
5672 }
5679 }
5687 }
5691 /*
5692 * we decide which is newer based on the RPMD on the name
5693 * attribute. See [MS-DRSR] ResolveNameConflict.
5694 *
5695 * We expect omd_name to be present, as this is from a local
5696 * search, but while rmd_name should have been given to us by
5697 * the remote server, if it is missing we just prefer the
5698 * local name in
5699 * replmd_replPropertyMetaData1_new_should_be_taken()
5700 */
5704 DEBUG(0,(__location__ ": Failed to find name attribute in local LDB replPropertyMetaData for %s\n",
5707 }
5709 /*
5710 * Should we preserve the current record, and so rename the
5711 * incoming record to be a conflict?
5712 */
5713 rename_incoming_record =
5730 }
5742 }
5747 }
5749 /* we are renaming the existing record */
5756 }
5765 }
5778 }
5780 /*
5781 * now we need to ensure that the rename is seen as an
5782 * originating update. We do that with a modify.
5783 */
5787 }
5789 DEBUG(2,(__location__ ": With conflicting record renamed, re-apply replicated rename '%s' -> '%s'\n",
5802 }
5806 failed:
5807 /*
5808 * On failure make the caller get the error
5809 * This means replication will stop with an error,
5810 * but there is not much else we can do. In the
5811 * LDB_ERR_ENTRY_ALREADY_EXISTS case this is exactly what is
5812 * needed.
5813 */
5816 }
5820 }
5824 {
5847 NTSTATUS nt_status;
5852 NTTIME now;
5865 /* find existing meta data */
5873 }
5877 }
5878 }
5889 s,
5897 rmd)));
5906 }
5913 /*
5914 * Fill in the remote_parent_guid with the GUID or an all-zero
5915 * GUID.
5916 */
5921 }
5923 /*
5924 * To ensure we follow a complex rename chain around, we have
5925 * to confirm that the DN is the same (mostly to confirm the
5926 * RDN) and the parentGUID is the same.
5927 *
5928 * This ensures we keep things under the correct parent, which
5929 * replmd_replicated_handle_rename() will do.
5930 */
5936 /*
5937 * handle renames, even just by case that come in over
5938 * DRS. Changes in the parent DN don't hit us here,
5939 * because the search for a parent will clean up those
5940 * components.
5941 *
5942 * We also have already filtered out the case where
5943 * the peer has an older name to what we have (see
5944 * replmd_replicated_apply_search_callback())
5945 */
5947 }
5956 }
5959 /*
5960 * Set the callback to one that will fix up the name
5961 * metadata on the new conflict DN
5962 */
5964 }
5974 /* first copy the old meta data */
5977 ni++;
5978 }
5981 /* now merge in the new meta data */
5990 }
5997 /* replace the entry */
6003 }
6004 }
6015 }
6018 }
6025 }
6027 /* we don't want to apply this change so remove the attribute */
6029 removed_attrs++;
6033 }
6042 }
6043 }
6054 }
6055 ni++;
6056 }
6058 /*
6059 * finally correct the size of the meta_data array
6060 */
6071 ldb_asprintf_errstring(ldb, "%s: error during DRS repl merge: %s", __func__, ldb_errstring(ldb));
6073 }
6074 }
6075 /*
6076 * sort the new meta data array
6077 */
6080 ldb_asprintf_errstring(ldb, "%s: error during DRS repl merge: %s", __func__, ldb_errstring(ldb));
6082 }
6084 /*
6085 * Work out if this object is deleted, so we can prune any extra attributes. See MS-DRSR 4.1.10.6.9
6086 * UpdateObject.
6087 *
6088 * This also controls SD propagation below
6089 */
6094 }
6098 /*
6099 * check if some replicated attributes left, otherwise skip the ldb_modify() call
6100 */
6106 }
6113 }
6121 }
6122 }
6124 /* create the meta data value */
6130 }
6132 /*
6133 * when we know that we'll modify the record, add the whenChanged, uSNChanged
6134 * and replPopertyMetaData attributes
6135 */
6136 ret = ldb_msg_add_string(msg, "whenChanged", ar->objs->objects[ar->index_current].when_changed);
6139 }
6143 }
6147 }
6151 /* we want to replace the old values */
6160 }
6161 }
6162 }
6168 LDB_CHANGETYPE_MODIFY,
6169 msg);
6173 s));
6182 }
6185 ldb,
6186 ar,
6187 msg,
6189 ar,
6190 callback,
6195 /* current partition control needed by "repmd_op_callback" */
6197 DSDB_CONTROL_CURRENT_PARTITION_OID,
6202 }
6206 {
6213 LDB_ERR_OPERATIONS_ERROR);
6214 }
6219 }
6227 /* we ignore referrals */
6231 {
6243 /*
6244 * This is the ADD case, find the appropriate parent,
6245 * as this object doesn't exist locally:
6246 */
6251 }
6254 }
6256 /*
6257 * Otherwise, in the MERGE case, work out if we are
6258 * attempting a rename, and if so find the parent the
6259 * newly renamed object wants to belong under (which
6260 * may not be the parent in it's attached string DN
6261 */
6266 /* find existing meta data */
6275 }
6279 }
6280 }
6288 "as local object has an all-zero parentGUID attribute, "
6292 }
6294 /*
6295 * now we need to check for double renames. We could have a
6296 * local rename pending which our replication partner hasn't
6297 * received yet. We choose which one wins by looking at the
6298 * attribute stamps on the two objects, the newer one wins.
6299 *
6300 * This also simply applies the correct algorithms for
6301 * determining if a change was made to name at all, or
6302 * if the object has just been renamed under the same
6303 * parent.
6304 */
6308 DEBUG(0,(__location__ ": Failed to find name attribute in local LDB replPropertyMetaData for %s\n",
6311 }
6313 /*
6314 * if there is no name attribute given then we have to assume the
6315 * object we've received has the older name
6316 */
6324 /* Merge on the existing object, with rename */
6339 /*
6340 * Merge on the existing object, force no
6341 * rename (code below just to explain why in
6342 * the DEBUG() logs)
6343 */
6357 }
6366 }
6367 /*
6368 * This assignment ensures that the strcmp()
6369 * and GUID_equal() calls in
6370 * replmd_replicated_apply_merge() avoids the
6371 * rename call
6372 */
6378 }
6381 }
6382 }
6383 }
6387 }
6389 /**
6390 * Stores the linked attributes received in the replication chunk - these get
6391 * applied at the end of the transaction. We also check that each linked
6392 * attribute is valid, i.e. source and target objects are known.
6393 */
6395 {
6407 /* save away the linked attributes for the end of the transaction */
6413 }
6418 }
6424 }
6428 /* we need to steal the non-scalars so they stay
6429 around until the end of the transaction */
6437 }
6440 }
6443 }
6448 {
6462 /*
6463 * Now that we've applied all the objects, check the new linked
6464 * attributes and store them (we apply them in .prepare_commit)
6465 */
6470 }
6472 /* done applying objects, move on to the next stage */
6474 }
6487 ldb,
6488 ar,
6490 LDB_SCOPE_SUBTREE,
6491 filter,
6492 attrs,
6493 NULL,
6494 ar,
6495 replmd_replicated_apply_search_callback,
6503 }
6506 }
6508 /*
6509 * This is essentially a wrapper for replmd_replicated_apply_next()
6510 *
6511 * This is needed to ensure that both codepaths call this handler.
6512 */
6514 {
6519 if (ar->isDeleted && (ret != LDB_SUCCESS || ldb_dn_compare(msg->dn, deleted_objects_dn) != 0)) {
6520 /*
6521 * Do a delete here again, so that if there is
6522 * anything local that conflicts with this
6523 * object being deleted, it is removed. This
6524 * includes links. See MS-DRSR 4.1.10.6.9
6525 * UpdateObject.
6526 *
6527 * If the object is already deleted, and there
6528 * is no more work required, it doesn't do
6529 * anything.
6530 */
6532 /* This has been updated to point to the DN we eventually did the modify on */
6541 }
6548 }
6550 /* Build a delete request, which hopefully will artually turn into nothing */
6553 NULL,
6554 res,
6555 ldb_modify_default_callback,
6561 }
6563 /*
6564 * This is the guts of the call, call back
6565 * into our delete code, but setting the
6566 * re_delete flag so we delete anything that
6567 * shouldn't be there on a deleted or recycled
6568 * object
6569 */
6573 }
6578 }
6579 }
6583 }
6587 {
6595 LDB_ERR_OPERATIONS_ERROR);
6596 }
6600 }
6605 LDB_ERR_OPERATIONS_ERROR);
6606 }
6611 }
6614 {
6633 NTTIME now;
6647 /* this happens for a REPL_OBJ call where we are
6648 creating the target object by replicating it. The
6649 subdomain join code does this for the partition DN
6650 */
6653 }
6660 }
6662 /*
6663 * first create the new replUpToDateVector
6664 */
6672 }
6676 }
6677 }
6679 /*
6680 * the new uptodateness vector will at least
6681 * contain 1 entry, one for the source_dsa
6682 *
6683 * plus optional values from our old vector and the one from the source_dsa
6684 */
6690 if (!nuv.ctr.ctr2.cursors) return replmd_replicated_request_werror(ar, WERR_NOT_ENOUGH_MEMORY);
6692 /* first copy the old vector */
6695 ni++;
6696 }
6698 /* merge in the source_dsa vector is available */
6705 }
6711 }
6717 }
6719 }
6723 /* if it's not there yet, add it */
6725 ni++;
6726 }
6728 /*
6729 * finally correct the size of the cursors array
6730 */
6733 /*
6734 * sort the cursors
6735 */
6738 /*
6739 * create the change ldb_message
6740 */
6750 }
6754 }
6757 /*
6758 * now create the new repsFrom value from the given repsFromTo1 structure
6759 */
6767 /*
6768 * first see if we already have a repsFrom value for the current source dsa
6769 * if so we'll later replace this value
6770 */
6784 }
6788 }
6790 /*
6791 * we compare the source dsa objectGUID not the invocation_id
6792 * because we want only one repsFrom value per source dsa
6793 * and when the invocation_id of the source dsa has changed we don't need
6794 * the old repsFrom with the old invocation_id
6795 */
6800 }
6805 }
6807 /*
6808 * copy over all old values to the new ldb_message
6809 */
6813 }
6815 /*
6816 * if we haven't found an old repsFrom value for the current source dsa
6817 * we'll add a new value
6818 */
6826 }
6828 /* we now fill the value which is already attached to ldb_message */
6835 }
6837 /*
6838 * the ldb_message_element for the attribute, has all the old values and the new one
6839 * so we'll replace the whole attribute with all values
6840 */
6845 LDB_CHANGETYPE_MODIFY,
6846 msg);
6849 }
6851 /* prepare the ldb_modify() request */
6853 ldb,
6854 ar,
6855 msg,
6857 ar,
6858 replmd_replicated_uptodate_modify_callback,
6864 }
6868 {
6875 LDB_ERR_OPERATIONS_ERROR);
6876 }
6881 }
6889 /* we ignore referrals */
6896 }
6897 }
6901 }
6905 {
6915 NULL
6916 };
6921 /*
6922 * Let the caller know that we did an originating updates
6923 */
6927 ldb,
6928 ar,
6930 LDB_SCOPE_BASE,
6932 attrs,
6933 NULL,
6934 ar,
6935 replmd_replicated_uptodate_search_callback,
6941 }
6945 static int replmd_extended_replicated_objects(struct ldb_module *module, struct ldb_request *req)
6946 {
6959 ldb_debug(ldb, LDB_DEBUG_FATAL, "replmd_extended_replicated_objects: invalid extended data\n");
6961 }
6964 ldb_debug(ldb, LDB_DEBUG_FATAL, "replmd_extended_replicated_objects: extended data invalid version [%u != %u]\n",
6967 }
6973 /* Set the flags to have the replmd_op_callback run over the full set of objects */
6982 }
6990 }
6995 }
6997 /* If this change contained linked attributes in the body
6998 * (rather than in the links section) we need to update
6999 * backlinks in linked_attributes */
7003 }
7009 }
7011 /**
7012 * Checks how to handle an missing target - either we need to fail the
7013 * replication and retry with GET_TGT, ignore the link and continue, or try to
7014 * add a partial link to an unknown target.
7015 */
7025 {
7029 /*
7030 * we may not be able to resolve link targets properly when
7031 * dealing with subsets of objects, e.g. the source is a
7032 * critical object and the target isn't
7033 *
7034 * TODO:
7035 * When we implement Trusted Domains we need to consider
7036 * whether they get treated as an incomplete replica here or not
7037 */
7040 /*
7041 * Ignore the link. We don't increase the highwater-mark in
7042 * the object subset cases, so subsequent replications should
7043 * resolve any missing links
7044 */
7050 }
7054 /*
7055 * target should already be up-to-date so there's no point in
7056 * retrying. This could be due to bad timing, or if a target
7057 * on a one-way link was deleted. We ignore the link rather
7058 * than failing the replication cycle completely
7059 */
7065 }
7068 mem_ctx,
7069 source_dn,
7070 target_dn);
7072 /* fail the replication and retry with GET_TGT */
7074 missing_str,
7079 }
7081 /*
7082 * The target of the cross-partition link is missing. Continue
7083 * and try to at least add the forward-link. This isn't great,
7084 * but a partial link can be fixed by dbcheck, so it's better
7085 * than dropping the link completely.
7086 */
7091 /*
7092 * Only log this when we're actually committing the objects.
7093 * This avoids spurious logs, i.e. if we're just verifying the
7094 * received link during a join.
7095 */
7099 }
7102 }
7104 /**
7105 * Checks that the target object for a linked attribute exists.
7106 * @param guid returns the target object's GUID (is returned)if it exists)
7107 * @param ignore_link set to true if the linked attribute should be ignored
7108 * (i.e. the target doesn't exist, but that it's OK to skip the link)
7109 */
7117 {
7123 NTSTATUS ntstatus;
7133 /*
7134 * This strange behaviour (allowing a NULL/missing
7135 * GUID) originally comes from:
7136 *
7137 * commit e3054ce0fe0f8f62d2f5b2a77893e7a1479128bd
7138 * Author: Andrew Tridgell <tridge@samba.org>
7139 * Date: Mon Dec 21 21:21:55 2009 +1100
7140 *
7141 * s4-drs: cope better with NULL GUIDS from DRS
7142 *
7143 * It is valid to get a NULL GUID over DRS for a deleted forward link. We
7144 * need to match by DN if possible when seeing if we should update an
7145 * existing link.
7146 *
7147 * Pair-Programmed-With: Andrew Bartlett <abartlet@samba.org>
7148 */
7151 DSDB_FLAG_NEXT_MODULE |
7152 DSDB_SEARCH_SHOW_RECYCLED |
7153 DSDB_SEARCH_SEARCH_ALL_PARTITIONS |
7154 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT,
7155 NULL);
7157 ldb_asprintf_errstring(ldb, "Failed to find GUID in linked attribute 0x%x blob for %s from %s",
7166 attrs,
7167 DSDB_FLAG_NEXT_MODULE |
7168 DSDB_SEARCH_SHOW_RECYCLED |
7169 DSDB_SEARCH_SEARCH_ALL_PARTITIONS |
7170 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT,
7171 NULL,
7174 }
7182 }
7186 /*
7187 * target object is unknown. Check whether to ignore the link,
7188 * fail the replication, or add a partial link
7189 */
7204 /* Get the object's state (i.e. Not Deleted, Tombstone, etc) */
7208 /*
7209 * Check for deleted objects as per MS-DRSR 4.1.10.6.14
7210 * ProcessLinkValue(). Link updates should not be sent for
7211 * recycled and tombstone objects (deleting the links should
7212 * happen when we delete the object). This probably means our
7213 * copy of the target object isn't up to date.
7214 */
7217 /*
7218 * target object is deleted. Check whether to ignore the
7219 * link, fail the replication, or add a partial link
7220 */
7226 }
7227 }
7231 }
7233 /**
7234 * Extracts the key details about the source/target object for a
7235 * linked-attribute entry.
7236 * This returns the following details:
7237 * @param ret_attr the schema details for the linked attribute
7238 * @param source_msg the search result for the source object
7239 * @param target_dsdb_dn the unpacked DN info for the target object
7240 */
7247 {
7253 WERROR status;
7257 /*
7258 linked_attributes[0]:
7259 &objs->linked_attributes[i]: struct drsuapi_DsReplicaLinkedAttribute
7260 identifier : *
7261 identifier: struct drsuapi_DsReplicaObjectIdentifier
7262 __ndr_size : 0x0000003a (58)
7263 __ndr_size_sid : 0x00000000 (0)
7264 guid : 8e95b6a9-13dd-4158-89db-3220a5be5cc7
7265 sid : S-0-0
7266 __ndr_size_dn : 0x00000000 (0)
7267 dn : ''
7268 attid : DRSUAPI_ATTID_member (0x1F)
7269 value: struct drsuapi_DsAttributeValue
7270 __ndr_size : 0x0000007e (126)
7271 blob : *
7272 blob : DATA_BLOB length=126
7273 flags : 0x00000001 (1)
7274 1: DRSUAPI_DS_LINKED_ATTRIBUTE_FLAG_ACTIVE
7275 originating_add_time : Wed Sep 2 22:20:01 2009 EST
7276 meta_data: struct drsuapi_DsReplicaMetaData
7277 version : 0x00000015 (21)
7278 originating_change_time : Wed Sep 2 23:39:07 2009 EST
7279 originating_invocation_id: 794640f3-18cf-40ee-a211-a93992b67a64
7280 originating_usn : 0x000000000001e19c (123292)
7282 (for cases where the link is to a normal DN)
7283 &target: struct drsuapi_DsReplicaObjectIdentifier3
7284 __ndr_size : 0x0000007e (126)
7285 __ndr_size_sid : 0x0000001c (28)
7286 guid : 7639e594-db75-4086-b0d4-67890ae46031
7287 sid : S-1-5-21-2848215498-2472035911-1947525656-19924
7288 __ndr_size_dn : 0x00000022 (34)
7289 dn : 'CN=UOne,OU=TestOU,DC=vsofs8,DC=com'
7290 */
7292 /* find the attribute being modified */
7301 }
7303 /*
7304 * All attributes listed here must be dealt with in some way
7305 * by replmd_process_linked_attribute() otherwise in the case
7306 * of isDeleted: FALSE the modify will fail with:
7307 *
7308 * Failed to apply linked attribute change 'attribute 'isDeleted':
7309 * invalid modify flags on
7310 * 'CN=g1_1527570609273,CN=Users,DC=samba,DC=example,DC=com':
7311 * 0x0'
7312 *
7313 * This is becaue isDeleted is a Boolean, so FALSE is a
7314 * legitimate value (set by Samba's deletetest.py)
7315 */
7321 /*
7322 * get the existing message from the db for the object with
7323 * this GUID, returning attribute being modified. We will then
7324 * use this msg as the basis for a modify call
7325 */
7327 DSDB_FLAG_NEXT_MODULE |
7328 DSDB_SEARCH_SEARCH_ALL_PARTITIONS |
7329 DSDB_SEARCH_SHOW_RECYCLED |
7330 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT |
7331 DSDB_SEARCH_REVEAL_INTERNALS,
7332 NULL,
7336 }
7341 }
7345 /* the value blob for the attribute holds the target object DN */
7353 }
7358 }
7360 /**
7361 * Verifies the source and target objects are known for a linked attribute
7362 */
7365 {
7378 /*
7379 * When we fail to find the source object, the error code we pass
7380 * back here is really important. It flags back to the callers to
7381 * retry this request with DRSUAPI_DRS_GET_ANC. This case should
7382 * never happen if we're replicating from a Samba DC, but it is
7383 * needed to talk to a Windows DC
7384 */
7387 }
7392 }
7394 /*
7395 * We can skip the target object checks if we're only syncing critical
7396 * objects, or we know the target is up-to-date. If either case, we
7397 * still continue even if the target doesn't exist
7398 */
7405 }
7407 /*
7408 * When we fail to find the target object, the error code we pass
7409 * back here is really important. It flags back to the callers to
7410 * retry this request with DRSUAPI_DRS_GET_TGT
7411 */
7414 }
7418 }
7420 /**
7421 * Finds the current active Parsed-DN value for a single-valued linked
7422 * attribute, if one exists.
7423 * @param ret_pdn assigned the active Parsed-DN, or NULL if none was found
7424 * @returns LDB_SUCCESS (regardless of whether a match was found), unless
7425 * an error occurred
7426 */
7433 {
7440 /* nothing to do for multi-valued linked attributes */
7442 }
7448 /* skip any inactive links */
7451 }
7453 /* we've found an active value for this attribute */
7461 }
7464 }
7466 /* no active link found */
7468 }
7470 /**
7471 * @returns true if the replication linked attribute info is newer than we
7472 * already have in our DB
7473 * @param pdn the existing linked attribute info in our DB
7474 * @param la the new linked attribute info received during replication
7475 */
7478 {
7479 /* see if this update is newer than what we have already */
7486 /* no existing info so update is newer */
7488 }
7496 version,
7498 change_time,
7500 }
7502 /**
7503 * Marks an existing linked attribute value as deleted in the DB
7504 * @param pdn the parsed-DN of the target-value to delete
7505 */
7517 {
7520 NTTIME now;
7530 }
7532 /* if the existing link is active, remove its backlink */
7540 }
7541 }
7543 /* mark the existing value as deleted */
7548 }
7550 /**
7551 * Checks for a conflict in single-valued link attributes, and tries to
7552 * resolve the problem if possible.
7553 *
7554 * Single-valued links should only ever have one active value. If we already
7555 * have an active link value, and during replication we receive an active link
7556 * value for a different target DN, then we need to resolve this inconsistency
7557 * and determine which value should be active. If the received info is better/
7558 * newer than the existing link attribute, then we need to set our existing
7559 * link as deleted. If the received info is worse/older, then we should continue
7560 * to add it, but set it as an inactive link.
7561 *
7562 * Note that this is a corner-case that is unlikely to happen (but if it does
7563 * happen, we don't want it to break replication completely).
7564 *
7565 * @param pdn_being_modified the parsed DN corresponding to the received link
7566 * target (note this is NULL if the link does not already exist in our DB)
7567 * @param pdn_list all the source object's Parsed-DNs for this attribute, i.e.
7568 * any existing active or inactive values for the attribute in our DB.
7569 * @param dsdb_dn the target DN for the received link attribute
7570 * @param add_as_inactive gets set to true if the received link is worse than
7571 * the existing link - it should still be added, but as an inactive link.
7572 */
7586 {
7591 /*
7592 * check if there's a conflict for single-valued links, i.e. an active
7593 * linked attribute already exists, but it has a different target value
7594 */
7601 }
7603 /*
7604 * If no active value exists (or the received info is for the currently
7605 * active value), then no conflict exists
7606 */
7609 }
7614 /* Work out how to resolve the conflict based on which info is better */
7622 /*
7623 * Delete our existing active link. The received info will then
7624 * be added (through normal link processing) as the active value
7625 */
7634 }
7640 /*
7641 * we want to keep our existing active link and add the
7642 * received link as inactive
7643 */
7645 }
7648 }
7650 /*
7651 process one linked attribute structure
7652 */
7657 {
7678 /*
7679 * get the attribute being modified, the search result for the source object,
7680 * and the target object's DN details
7681 */
7688 }
7690 /*
7691 * Check for deleted objects per MS-DRSR 4.1.10.6.14
7692 * ProcessLinkValue, because link updates are not applied to
7693 * recycled and tombstone objects. We don't have to delete
7694 * any existing link, that should have happened when the
7695 * object deletion was replicated or initiated.
7696 *
7697 * This needs isDeleted and isRecycled to be included as
7698 * attributes in the search and so in msg if set.
7699 */
7705 }
7707 /*
7708 * Now that we know the deletion_state, remove the extra
7709 * attributes added for that purpose. We need to do this
7710 * otherwise in the case of isDeleted: FALSE the modify will
7711 * fail with:
7712 *
7713 * Failed to apply linked attribute change 'attribute 'isDeleted':
7714 * invalid modify flags on
7715 * 'CN=g1_1527570609273,CN=Users,DC=samba,DC=example,DC=com':
7716 * 0x0'
7717 *
7718 * This is becaue isDeleted is a Boolean, so FALSE is a
7719 * legitimate value (set by Samba's deletetest.py)
7720 */
7732 }
7735 }
7737 /* parse the existing links */
7744 }
7752 }
7754 /*
7755 * there are some cases where the target object doesn't exist, but it's
7756 * OK to ignore the linked attribute
7757 */
7761 }
7763 /* see if this link already exists */
7774 }
7782 }
7784 /* get a seq_num for this change */
7789 }
7791 /*
7792 * check for single-valued link conflicts, i.e. an active linked
7793 * attribute already exists, but it has a different target value
7794 */
7800 seq_num,
7805 }
7806 }
7812 /* remove the existing backlink */
7814 schema,
7817 parent);
7821 }
7822 }
7830 /*
7831 * We know where the new one needs to be, from the *next
7832 * pointer into pdn_list.
7833 */
7842 }
7843 }
7848 }
7849 }
7856 }
7861 }
7867 }
7869 /* set the link attribute's value to the info that was received */
7879 }
7883 /* Set the new link as inactive/deleted to avoid conflicts */
7887 val_to_update);
7892 }
7896 /* if the new link is active, then add the new backlink */
7898 schema,
7901 parent);
7905 }
7906 }
7908 /* we only change whenChanged and uSNChanged if the seq_num
7909 has changed */
7915 }
7922 }
7928 }
7934 }
7943 tmp_ctx,
7944 LDB_CHANGETYPE_MODIFY,
7945 msg));
7948 }
7953 }
7956 {
7959 }
7962 }
7965 /*
7966 we hook into the transaction operations to allow us to
7967 perform the linked attribute updates at the end of the whole
7968 transaction. This allows a forward linked attribute to be created
7969 before the object is created. During a vampire, w2k8 sends us linked
7970 attributes before the objects they are part of.
7971 */
7973 {
7974 /* create our private structure for this transaction */
7979 /* free any leftover mod_usn records from cancelled
7980 transactions */
7985 }
7990 }
7992 /*
7993 on prepare commit we loop over our queued la_context structures and
7994 apply each of them
7995 */
7997 {
8003 /*
8004 * Walk the list of linked attributes from DRS replication.
8005 *
8006 * We walk backwards, to do the first entry first, as we
8007 * added the entries with DLIST_ADD() which puts them at the
8008 * start of the list
8009 */
8018 }
8019 }
8023 /* possibly change @REPLCHANGED */
8027 }
8030 }
8033 {
8039 }
8053 };
8056 {
8059 }