| blob | 871e1d56ec2d05aeaad82aed6546552b8fb1d28d |
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 */
55 #undef strcasecmp
57 #undef DBGC_CLASS
58 #define DBGC_CLASS DBGC_DRS_REPL
60 /* the RMD_VERSION for linked attributes starts from 1 */
61 #define RMD_VERSION_INITIAL 1
63 /*
64 * It's 29/12/9999 at 23:59:59 UTC as specified in MS-ADTS 7.1.1.4.2
65 * Deleted Objects Container
66 */
85 };
87 /*
88 * groups link attributes together by source-object and attribute-ID,
89 * to improve processing efficiency (i.e. for 'member' attribute, which
90 * could have 100s or 1000s of links).
91 * Note this grouping is best effort - the same source object could still
92 * correspond to several la_groups (a lot depends on the order DRS sends
93 * the links in). The groups currently don't span replication chunks (which
94 * caps the size to ~1500 links by default).
95 */
99 };
105 };
114 /* the controls we pass down */
117 /*
118 * Backlinks for the replmd_add() case (we want to create
119 * backlinks after creating the user, but before the end of
120 * the ADD request)
121 */
124 /* details for the mode where we apply a bunch of inbound replication meessages */
138 };
140 /*
141 * the result of replmd_process_linked_attribute(): either there was no change
142 * (update was ignored), a new link was added (either inactive or active), or
143 * an existing link was modified (active/inactive status may have changed).
144 */
146 LINK_CHANGE_NONE,
147 LINK_CHANGE_ADDED,
148 LINK_CHANGE_MODIFIED,
152 static int replmd_delete_internals(struct ldb_module *module, struct ldb_request *req, bool re_delete);
183 };
191 };
194 {
200 /*
201 * only lookup the recycle-bin state once per replication, then cache
202 * the result. This can save us 1000s of DB searches
203 */
208 }
212 }
215 }
221 {
228 }
230 }
239 }
241 }
247 }
249 }
254 }
256 }
261 }
267 }
268 }
281 };
283 /* Attributes looked for when updating or deleting, to check for a urgent replication needed */
288 NULL
289 };
294 {
300 }
306 }
307 }
308 }
310 }
313 {
316 }
318 }
322 /*
323 initialise the module
324 allocate the private structure and build the list
325 of partition DNs for use by replmd_notify()
326 */
328 {
337 }
340 SAMBA_SORTED_LINKS_FEATURE,
345 }
350 }
352 /*
353 cleanup our per-transaction contexts
354 */
356 {
361 }
370 };
372 /*
373 a ldb_modify request operating on modules below the
374 current module
375 */
379 {
390 }
393 message,
394 NULL,
395 res,
396 ldb_modify_default_callback,
397 parent);
402 }
408 }
410 /* Run the new request */
415 }
419 }
421 /*
422 process a backlinks we accumulated during a transaction, adding and
423 deleting the backlinks from the target objects
424 */
425 static int replmd_process_backlink(struct ldb_module *module, struct la_backlink *bl, struct ldb_request *parent)
426 {
434 /*
435 - find DN of target
436 - find DN of source
437 - construct ldb_message
438 - either an add or a delete
439 */
448 }
455 }
463 /* Filter down to the attributes we want in the backlink */
466 }
468 /* construct a ldb_message for adding/deleting the backlink */
475 }
480 }
483 /* a backlink should never be single valued. Unfortunately the
484 exchange schema has a attribute
485 msExchBridgeheadedLocalConnectorsDNBL which is single
486 valued and a backlink. We need to cope with that by
487 ignoring the single value flag */
492 /* we allow LDB_ERR_NO_SUCH_ATTRIBUTE as success to
493 cope with possible corruption where the backlink has
494 already been removed */
508 }
511 }
513 /*
514 add a backlink to the list of backlinks to add/delete in the prepare
515 commit
517 forward_dn is stolen onto the defereed context
518 */
527 {
535 }
539 /*
540 * windows 2003 has a broken schema where the
541 * definition of msDS-IsDomainFor is missing (which is
542 * supposed to be the backlink of the
543 * msDS-HasDomainNCs attribute
544 */
546 }
556 }
558 /*
559 add a backlink to the list of backlinks to add/delete in the prepare
560 commit
561 */
569 {
576 /*
577 * windows 2003 has a broken schema where the
578 * definition of msDS-IsDomainFor is missing (which is
579 * supposed to be the backlink of the
580 * msDS-HasDomainNCs attribute
581 */
583 }
592 }
595 /*
596 * Callback for most write operations in this module:
597 *
598 * notify the repl task that a object has changed. The notifies are
599 * gathered up in the replmd_private structure then written to the
600 * @REPLCHANGED object in each partition during the prepare_commit
601 */
603 {
620 /*
621 * Remove the current partition control from what we pass up
622 * the chain if it hasn't been requested manually.
623 */
625 partition_ctrl);
626 }
638 }
641 /*
642 * Set at DBG_NOTICE as once these start to happe, they
643 * will happen a lot until resolved, due to repeated
644 * replication. The caller will probably print the
645 * ldb error string anyway.
646 */
652 ac,
653 LDB_CHANGETYPE_ADD,
654 msg);
660 s);
664 }
670 }
674 /*
675 * process our backlink list after an replmd_add(),
676 * creating and deleting backlinks as necessary (this
677 * code is sync). The other cases are handled inline
678 * with the modify.
679 */
685 }
686 }
687 }
693 }
703 }
704 }
712 }
718 }
720 }
726 }
727 }
730 }
731 }
737 }
740 /* free the partition control container here, for the
741 * common path. Other cases will have it cleaned up
742 * eventually with the ares */
746 }
747 }
750 /*
751 * update a @REPLCHANGED record in each partition if there have been
752 * any writes of replicated data in the partition
753 */
755 {
770 }
778 DSDB_EXTENDED_SCHEMA_UPDATE_NOW_OID,
779 ext_res,
780 DSDB_FLAG_NEXT_MODULE,
781 parent);
784 }
786 }
790 }
793 }
796 /*
797 created a replmd_replicated_request context
798 */
801 {
812 }
824 }
826 /* get our invocationId */
833 }
837 }
839 /*
840 add a time element to a record
841 */
843 {
850 }
855 }
860 }
863 /* always set as replace. This works because on add ops, the flag
864 is ignored */
868 }
870 /*
871 add a uint64_t element to a record
872 */
875 {
881 }
886 }
889 /* always set as replace. This works because on add ops, the flag
890 is ignored */
894 }
898 {
899 /*
900 * This assignment seems inoccous, but it is critical for the
901 * system, as we need to do the comparisons as a unsigned
902 * quantity, not signed (enums are signed integers)
903 */
909 }
911 /*
912 * See above regarding this being an unsigned comparison.
913 * Otherwise when the high bit is set on non-standard
914 * attributes, they would end up first, before objectClass
915 * (0).
916 */
918 }
923 {
929 }
931 /* the objectClass attribute is value 0x00000000, so must be first */
937 }
940 }
945 {
946 /* Note this is O(n^2) for the almost-sorted case, which this is */
948 replmd_replPropertyMetaData1_attid_sort);
950 }
955 {
959 /*
960 * TODO: make this faster by caching the dsdb_attribute pointer
961 * on the ldb_messag_element
962 */
967 /*
968 * TODO: remove this check, we should rely on e1 and e2 having valid attribute names
969 * in the schema
970 */
973 }
976 }
978 }
982 {
983 LDB_TYPESAFE_QSORT(msg->elements, msg->num_elements, schema, replmd_ldb_message_element_attid_sort);
984 }
1000 /*
1001 fix up linked attributes in replmd_add.
1002 This involves setting up the right meta-data in extended DN
1003 components, and creating backlinks to the object
1004 */
1009 NTTIME now,
1013 {
1018 /* We will take a reference to the schema in replmd_add_backlink */
1027 "Attribute %s is single valued but "
1032 }
1034 /*
1035 * At the successful end of these functions el->values is
1036 * overwritten with new_values. However get_parsed_dns()
1037 * points p->v at the supplied el and it effectively gets used
1038 * as a working area by replmd_build_la_val(). So we must
1039 * duplicate it because our caller only called
1040 * ldb_msg_copy_shallow().
1041 */
1050 }
1057 }
1063 }
1070 }
1080 }
1085 parent);
1089 }
1092 }
1097 }
1102 {
1105 /* Calculate an extended DN for any linked attributes */
1109 }
1113 }
1120 }
1121 }
1124 }
1126 /*
1127 intercept add requests
1128 */
1130 {
1138 DATA_BLOB guid_blob_stack;
1145 /*
1146 * The use of a time_t here seems odd, but as the NTTIME
1147 * elements are actually declared as NTTIME_1sec in the IDL,
1148 * getting a higher resolution timestamp is not required.
1149 */
1151 NTTIME now;
1165 /* check if there's a show relax control (used by provision to say 'I know what I'm doing') */
1169 }
1171 /* do not manipulate our control entries */
1174 }
1192 }
1193 /* we remove this attribute as it can be a string and
1194 * will not be treated correctly and then we will re-add
1195 * it later on in the good format */
1197 }
1199 /* a new GUID */
1204 /* This can't fail */
1208 }
1213 }
1217 /* Get a sequence number from the backend */
1222 }
1224 /* we have to copy the message as the caller might have it as a const */
1230 }
1232 /* generated times */
1239 }
1242 }
1244 /*
1245 * remove autogenerated attributes
1246 */
1253 /*
1254 * readd replicated attributes
1255 */
1261 }
1263 /* build the replication meta_data */
1274 }
1284 i++;
1286 }
1295 }
1297 if ((sa->systemFlags & DS_FLAG_ATTR_NOT_REPLICATED) || (sa->systemFlags & DS_FLAG_ATTR_IS_CONSTRUCTED)) {
1298 /* if the attribute is not replicated (0x00000001)
1299 * or constructed (0x00000004) it has no metadata
1300 */
1301 i++;
1303 }
1308 guid_blob,
1313 }
1314 }
1316 /*
1317 * Prepare the context for the backlinks and
1318 * create metadata for the forward links. The
1319 * backlinks are created in
1320 * replmd_op_callback() after the successful
1321 * ADD of the object.
1322 */
1326 extended_dn,
1331 }
1332 /* linked attributes are not stored in
1333 replPropertyMetaData in FL above w2k */
1334 i++;
1336 }
1348 }
1352 /*
1353 * Set the originating_change_time to 29/12/9999 at 23:59:59
1354 * as specified in MS-ADTS 7.1.1.4.2 Deleted Objects Container
1355 */
1359 }
1362 }
1366 ni++;
1369 i++;
1371 }
1376 i++;
1378 }
1381 }
1383 /* fix meta data count */
1386 /*
1387 * sort meta data array
1388 */
1394 }
1396 /* generated NDR encoded values */
1404 }
1406 /*
1407 * add the autogenerated values
1408 */
1414 }
1420 }
1426 }
1432 }
1438 }
1440 /*
1441 * sort the attributes by attid before storing the object
1442 */
1445 /*
1446 * Assert that we do have an objectClass
1447 */
1455 }
1457 REPL_URGENT_ON_CREATE);
1461 msg,
1464 req);
1470 }
1472 /* current partition control is needed by "replmd_op_callback" */
1475 DSDB_CONTROL_CURRENT_PARTITION_OID,
1480 }
1481 }
1488 }
1489 }
1491 /* mark the relax control done */
1494 }
1495 /* go on with the call chain */
1497 }
1500 /*
1501 * update the replPropertyMetaData for one element
1502 */
1511 NTTIME now,
1515 {
1525 /* allow this to make it possible for dbcheck
1526 to remove bad attributes */
1528 }
1533 }
1537 if ((a->systemFlags & DS_FLAG_ATTR_NOT_REPLICATED) || (a->systemFlags & DS_FLAG_ATTR_IS_CONSTRUCTED)) {
1539 }
1541 /*
1542 * if the attribute's value haven't changed, and this isn't
1543 * just a delete of everything then return LDB_SUCCESS Unless
1544 * we have the provision control or if the attribute is
1545 * interSiteTopologyGenerator as this page explain:
1546 * http://support.microsoft.com/kb/224815 this attribute is
1547 * periodicaly written by the DC responsible for the intersite
1548 * generation in a given site
1549 *
1550 * Unchanged could be deleting or replacing an already-gone
1551 * thing with an unconstrained delete/empty replace or a
1552 * replace with the same value, but not an add with the same
1553 * value because that could be about adding a duplicate (which
1554 * is for someone else to error out on).
1555 */
1559 }
1565 }
1568 /*
1569 * We intentionally skip the version bump when attempting to
1570 * vanish links.
1571 *
1572 * The control is set by dbcheck and expunge-tombstones which
1573 * both attempt to be non-replicating. Otherwise, making an
1574 * alteration to the replication state would trigger a
1575 * broadcast of all expunged objects.
1576 */
1578 }
1583 }
1588 /*
1589 * allow this to make it possible for dbcheck
1590 * to rebuild broken metadata
1591 */
1593 }
1594 }
1597 /*
1598 * First check if we find it under the msDS-IntID,
1599 * then check if we find it under the OID and
1600 * prefixMap ID.
1601 *
1602 * This allows the administrator to simply re-write
1603 * the attributes and so restore replication, which is
1604 * likely what they will try to do.
1605 */
1608 }
1612 }
1613 }
1616 /* linked attributes are not stored in
1617 replPropertyMetaData in FL above w2k, but we do
1618 raise the seqnum for the object */
1622 }
1624 }
1627 /* we need to add a new one */
1633 }
1636 }
1638 /* Get a new sequence number from the backend. We only do this
1639 * if we have a change that requires a new
1640 * replPropertyMetaData element
1641 */
1646 }
1647 }
1660 }
1664 /*
1665 * Set the originating_change_time to 29/12/9999 at 23:59:59
1666 * as specified in MS-ADTS 7.1.1.4.2 Deleted Objects Container
1667 */
1671 }
1674 }
1680 /* Force version to 0 to be overridden later via replication */
1682 }
1685 }
1687 /*
1688 * Bump the replPropertyMetaData version on an attribute, and if it
1689 * has changed (or forced by leaving rdn_old NULL), update the value
1690 * in the entry.
1691 *
1692 * This is important, as calling a modify operation may not change the
1693 * version number if the values appear unchanged, but a rename between
1694 * parents bumps this value.
1695 *
1696 */
1703 NTTIME now,
1706 {
1712 rdn_name;
1718 };
1724 };
1730 }
1731 }
1739 }
1742 {
1750 }
1751 }
1753 }
1755 /*
1756 * update the replPropertyMetaData object each time we modify an
1757 * object. This is needed for DRS replication, as the merge on the
1758 * client is based on this object
1759 */
1767 {
1772 NTTIME now;
1791 }
1797 }
1805 }
1810 }
1814 /* this happens during an initial vampire while
1815 updating the schema */
1818 }
1826 }
1829 }
1831 /* if isDeleted is present and is TRUE, then we consider we are deleting,
1832 * otherwise we consider we are updating */
1839 }
1842 /* In this case the change_replmetadata control was supplied */
1843 /* We check that it's the only attribute that is provided
1844 * (it's a rare case so it's better to keep the code simplier)
1845 * We also check that the highest local_usn is bigger or the same as
1846 * uSNChanged. */
1854 }
1856 DEBUG(0,(__location__ ": changereplmetada control can't be called when deleting an object\n"));
1858 }
1864 }
1871 }
1874 DSDB_FLAG_NEXT_MODULE |
1875 DSDB_SEARCH_SHOW_RECYCLED |
1876 DSDB_SEARCH_SHOW_EXTENDED_DN |
1877 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT |
1882 }
1889 /*
1890 * The test here now allows for a new
1891 * replPropertyMetaData with no change, if was
1892 * just dbcheck re-sorting the values.
1893 */
1899 }
1900 }
1903 /* search for the existing replPropertyMetaDataBlob. We need
1904 * to use REVEAL and ask for DNs in storage format to support
1905 * the check for values being the same in
1906 * replmd_update_rpmd_element()
1907 */
1909 DSDB_FLAG_NEXT_MODULE |
1910 DSDB_SEARCH_SHOW_RECYCLED |
1911 DSDB_SEARCH_SHOW_EXTENDED_DN |
1912 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT |
1916 }
1923 }
1931 }
1937 }
1946 our_invocation_id,
1948 is_forced_rodc,
1949 req);
1952 }
1956 }
1959 i++;
1961 }
1966 i++;
1968 }
1971 }
1972 }
1974 /*
1975 * Assert that we have an objectClass attribute - this is major
1976 * corruption if we don't have this!
1977 */
1980 /*
1981 * Now check if this objectClass means we need to do urgent replication
1982 */
1984 situation)) {
1986 }
1992 }
1994 /*
1995 * replmd_update_rpmd_element has done an update if the
1996 * seq_num is set
1997 */
2002 /*if we are RODC and this is a DRSR update then its ok*/
2011 }
2017 }
2018 }
2024 }
2030 }
2038 }
2045 }
2049 }
2052 }
2055 {
2060 }
2062 }
2064 /*
2065 get a series of message element values as an array of DNs and GUIDs
2066 the result is sorted by GUID
2067 */
2071 {
2079 }
2085 }
2089 NTSTATUS status;
2098 }
2105 /* we got a DN without a GUID - go find the GUID */
2113 dn_str);
2118 }
2120 }
2124 }
2127 }
2132 }
2133 }
2134 /* keep a pointer to the original ldb_val */
2136 }
2139 }
2141 }
2143 /*
2144 * Get a series of trusted message element values. The result is sorted by
2145 * GUID, even though the GUIDs might not be known. That works because we trust
2146 * the database to give us the elements like that if the
2147 * replmd_private->sorted_links flag is set.
2148 *
2149 * We also ensure that the links are in the Functional Level 2003
2150 * linked attributes format.
2151 */
2159 {
2164 }
2167 /* We need to sort the list. This is the slow old path we want
2168 to avoid.
2169 */
2171 parent);
2174 }
2180 }
2181 }
2183 /*
2184 * This upgrades links to FL2003 style, and sorts the result
2185 * if that was needed.
2186 *
2187 * TODO: Add a database feature that asserts we have no FL2000
2188 * style links to avoid this check or add a feature that
2189 * uses a similar check to find sorted/unsorted links
2190 * for an on-the-fly upgrade.
2191 */
2195 el,
2196 ldap_oid);
2199 }
2202 }
2204 /*
2205 Return LDB_SUCCESS if a parsed_dn list contains no duplicate values,
2206 otherwise an error code. For compatibility the error code differs depending
2207 on whether or not the attribute is "member".
2209 As always, the parsed_dn list is assumed to be sorted.
2210 */
2214 {
2222 "Linked attribute %s has "
2229 }
2230 }
2231 }
2233 }
2235 /*
2236 build a new extended DN, including all meta data fields
2238 RMD_FLAGS = DSDB_RMD_FLAG_* bits
2239 RMD_ADDTIME = originating_add_time
2240 RMD_INVOCID = originating_invocation_id
2241 RMD_CHANGETIME = originating_change_time
2242 RMD_ORIGINATING_USN = originating_usn
2243 RMD_LOCAL_USN = local_usn
2244 RMD_VERSION = version
2245 */
2250 {
2254 }
2256 static int replmd_update_la_val(TALLOC_CTX *mem_ctx, struct ldb_val *v, struct dsdb_dn *dsdb_dn,
2261 /*
2262 check if any links need upgrading from w2k format
2263 */
2268 {
2272 NTSTATUS status;
2277 ldap_oid);
2280 }
2281 }
2286 /*
2287 * We optimistically assume they are all the same; if
2288 * the first one is fixed, they are all fixed.
2289 *
2290 * If the first one was *not* fixed and we find a
2291 * later one that is, that is an occasion to shout
2292 * with DEBUG(0).
2293 */
2296 }
2300 }
2306 }
2307 }
2310 /* it's an old one that needs upgrading */
2316 }
2317 }
2319 /*
2320 * This sort() is critical for the operation of
2321 * get_parsed_dns_trusted_fallback() because callers of this function
2322 * expect a sorted list, and FL2000 style links are not
2323 * sorted. In particular, as well as the upgrade case,
2324 * get_parsed_dns_trusted_fallback() is called from
2325 * replmd_delete_remove_link() even in FL2000 mode
2326 *
2327 * We do not normally pay the cost of the qsort() due to the
2328 * early return in the RMD_VERSION found case.
2329 */
2332 }
2334 /*
2335 Sets the value for a linked attribute, including all meta data fields
2337 see replmd_build_la_val for value names
2338 */
2343 {
2351 NTSTATUS status;
2360 }
2366 }
2372 }
2378 }
2383 }
2389 /* get the ADDTIME from the original */
2393 }
2396 }
2401 }
2403 /* use our invocation id */
2407 /* changetime is the current time */
2411 /* update the USN */
2426 }
2430 }
2432 /**
2433 * Updates the value for a linked attribute, including all meta data fields
2434 */
2435 static int replmd_update_la_val(TALLOC_CTX *mem_ctx, struct ldb_val *v, struct dsdb_dn *dsdb_dn,
2439 {
2442 NTSTATUS status;
2444 /*
2445 * We're updating the linked attribute locally, so increase the version
2446 * by 1 so that other DCs will see the change when it gets replicated out
2447 */
2453 }
2457 }
2459 /*
2460 handle adding a linked attribute
2461 */
2472 {
2482 NTTIME now;
2485 /* get the DNs to be added, fully parsed.
2486 *
2487 * We need full parsing because they came off the wire and we don't
2488 * trust them, besides which we need their details to know where to put
2489 * them.
2490 */
2496 }
2498 /* get the existing DNs, lazily parsed */
2502 parent);
2507 }
2516 }
2524 }
2526 /*
2527 * For each new value, find where it would go in the list. If there is
2528 * a matching GUID there, we update the existing value; otherwise we
2529 * put it in place.
2530 */
2546 }
2553 NTSTATUS status;
2559 }
2564 }
2566 /*
2567 * Only "<GUID=...><SID=...>" is allowed.
2568 *
2569 * We get the GUID to just to find the old
2570 * value and the SID in order to add it
2571 * to the found value.
2572 */
2578 }
2584 }
2589 /* this is what we expect */
2593 "i[%u] SID NOT MISSING... Attribute %s already "
2606 }
2613 "NO SID PROVIDED... Attribute %s already "
2620 }
2627 }
2634 }
2641 }
2643 /*
2644 * We just replace the existing value...
2645 */
2649 }
2652 /*
2653 * We are trying to add one that exists, which is only
2654 * allowed if it was previously deleted.
2655 *
2656 * When we do undelete a link we change it in place.
2657 * It will be copied across into the right spot in due
2658 * course.
2659 */
2666 "Attribute %s already "
2672 /* error codes for 'member' need to be
2673 special cased */
2678 }
2679 }
2690 }
2694 msg_dn,
2697 schema_attr,
2698 parent);
2702 }
2704 }
2705 /*
2706 * Here we don't have an exact match.
2707 *
2708 * If next is NULL, this one goes beyond the end of the
2709 * existing list, so we need to add all of those ones first.
2710 *
2711 * If next is not NULL, we need to add all the ones before
2712 * next.
2713 */
2717 /* next should have been parsed, but let's make sure */
2724 }
2725 }
2727 }
2729 /* put all the old ones before next on the list */
2732 num_values++;
2733 }
2739 parent);
2743 }
2744 /* Make the new linked attribute ldb_val. */
2751 }
2752 num_values++;
2756 }
2757 }
2758 /* copy the rest of the old ones (if any) */
2761 num_values++;
2762 }
2767 }
2773 /* we now tell the backend to replace all existing values
2774 with the one we have constructed */
2778 }
2781 /*
2782 handle deleting all active linked attributes
2783 */
2794 {
2804 NTTIME now;
2809 /* there is nothing to delete... */
2811 /* and we're deleting nothing, so that's OK */
2813 }
2815 }
2820 }
2827 }
2832 parent);
2837 }
2843 }
2845 /* we empty out el->values here to avoid damage if we return early. */
2849 /*
2850 * If vanish links is set, we are actually removing members of
2851 * old_el->values; otherwise we are just marking them deleted.
2852 *
2853 * There is a special case when no values are given: we remove them
2854 * all. When we have the vanish_links control we just have to remove
2855 * the backlinks and change our element to replace the existing values
2856 * with the empty list.
2857 */
2867 }
2868 }
2872 parent);
2876 }
2879 }
2884 }
2894 }
2895 }
2901 }
2902 }
2911 NULL,
2919 }
2932 }
2933 }
2943 "attribute %s to %s, because "
2946 }
2947 }
2949 /* remove the backlink */
2951 replmd_private,
2953 msg_dn,
2956 parent);
2960 }
2962 /* We flag the deletion and tidy it up later. */
2965 }
2981 }
2982 }
2992 }
2997 parent);
3001 }
3002 }
3013 }
3017 }
3019 j++;
3020 }
3023 }
3025 }
3032 /* we now tell the backend to replace all existing values
3033 with the one we have constructed */
3037 }
3039 /*
3040 handle replacing a linked attribute
3041 */
3052 {
3063 NTTIME now;
3067 /*
3068 * The replace operation is unlike the replace and delete cases in that
3069 * we need to look at every existing link to see whether it is being
3070 * retained or deleted. In other words, we can't avoid parsing the GUIDs.
3071 *
3072 * As we are trying to combine two sorted lists, the algorithm we use
3073 * is akin to the merge phase of a merge sort. We interleave the two
3074 * lists, doing different things depending on which side the current
3075 * item came from.
3076 *
3077 * There are three main cases, with some sub-cases.
3078 *
3079 * - a DN is in the old list but not the new one. It needs to be
3080 * marked as deleted (but left in the list).
3081 * - maybe it is already deleted, and we have less to do.
3082 *
3083 * - a DN is in both lists. The old data gets replaced by the new,
3084 * and the list doesn't grow. The old link may have been marked as
3085 * deleted, in which case we undelete it.
3086 *
3087 * - a DN is in the new list only. We add it in the right place.
3088 */
3095 /* There is nothing to do! */
3097 }
3099 /*
3100 * At the successful end of these functions el->values is
3101 * overwritten with new_values. However get_parsed_dns()
3102 * points p->v at the supplied el and it effectively gets used
3103 * as a working area by replmd_build_la_val(). So we must
3104 * duplicate it because our caller only called
3105 * ldb_msg_copy_shallow().
3106 */
3115 }
3121 }
3127 }
3134 }
3141 }
3148 }
3160 /* the new list is empty, read the old list */
3165 /* the old list is empty, read new list */
3171 }
3174 /*
3175 * An old ones that come before the next replacement
3176 * (if any). We mark it as deleted and add it to the
3177 * final list.
3178 */
3190 }
3194 msg_dn,
3196 schema_attr,
3197 parent);
3201 }
3202 }
3204 old_i++;
3206 /*
3207 * We are overwriting one. If it was previously
3208 * deleted, we need to add a backlink.
3209 *
3210 * Note that if any RMD_FLAGs in an extended new DN
3211 * will be ignored.
3212 */
3224 }
3230 msg_dn,
3232 schema_attr,
3233 parent);
3237 }
3238 }
3241 old_i++;
3242 new_i++;
3244 /*
3245 * Replacements that don't match an existing one. We
3246 * just add them to the final list.
3247 */
3256 }
3259 msg_dn,
3261 schema_attr,
3262 parent);
3266 }
3268 new_i++;
3269 }
3270 }
3273 }
3281 }
3284 /*
3285 handle linked attributes in modify requests
3286 */
3293 {
3301 /*
3302 * Nothing special is required for modifying or vanishing links
3303 * in fl2000 since they are just strings in a multi-valued
3304 * attribute.
3305 */
3307 DSDB_CONTROL_REPLMD_VANISH_LINKS);
3310 }
3312 }
3314 /*
3315 * TODO:
3316 *
3317 * We should restrict this to the intersection of the list of
3318 * linked attributes in the schema and the list of attributes
3319 * being modified.
3320 *
3321 * This will help performance a little, as otherwise we have
3322 * to allocate the entire object value-by-value.
3323 */
3325 DSDB_FLAG_NEXT_MODULE |
3326 DSDB_SEARCH_SHOW_RECYCLED |
3327 DSDB_SEARCH_REVEAL_INTERNALS |
3328 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT,
3329 parent);
3332 }
3347 }
3350 }
3355 DSDB_CONTROL_REPLMD_VANISH_LINKS);
3359 }
3361 DSDB_CONTROL_DBCHECK);
3364 }
3366 /* Odd is for the target. Illegal to modify */
3370 }
3378 parent);
3385 parent);
3392 parent);
3399 }
3402 }
3408 /* Return codes as found on Windows 2012r2 */
3413 }
3416 }
3420 }
3425 /* TODO: this relises a bit too heavily on the exact
3426 behaviour of ldb_msg_find_element and
3427 ldb_msg_remove_element */
3431 i--;
3432 }
3433 }
3437 }
3443 {
3449 WERROR werr;
3462 server_dn);
3463 }
3464 }
3468 }
3471 domain,
3476 }
3479 }
3483 {
3501 /* do not manipulate our control entries */
3504 }
3507 DSDB_CONTROL_SEC_DESC_PROPAGATION_OID);
3511 }
3516 }
3519 }
3524 DSDB_CONTROL_DBCHECK_FIX_DUPLICATE_LINKS);
3531 }
3535 }
3540 }
3546 }
3550 }
3554 }
3557 DSDB_CONTROL_DBCHECK_FIX_LINK_DN_NAME);
3564 }
3568 }
3572 }
3576 }
3580 }
3585 }
3590 }
3596 }
3600 }
3604 }
3606 /*
3607 * If we are run from dbcheck and we are not updating
3608 * a link (as these would need to be sorted and so
3609 * can't go via such a simple update, then do not
3610 * trigger replicated updates and a new USN from this
3611 * change, it wasn't a real change, just a new
3612 * (correct) string DN
3613 */
3617 }
3626 }
3631 }
3635 /* we have to copy the message as the caller might have it as a const */
3641 }
3644 DSDB_CONTROL_DBCHECK_FIX_LINK_DN_SID);
3651 }
3656 }
3661 }
3668 }
3673 }
3679 }
3694 }
3699 }
3701 handle_linked_attribs:
3707 }
3709 /* TODO:
3710 * - replace the old object with the newly constructed one
3711 */
3716 msg,
3719 req);
3724 }
3726 /* current partition control is needed by "replmd_op_callback" */
3729 DSDB_CONTROL_CURRENT_PARTITION_OID,
3734 }
3735 }
3737 /* If we are in functional level 2000, then
3738 * replmd_modify_handle_linked_attribs will have done
3739 * nothing */
3745 }
3746 }
3750 /* we only change whenChanged and uSNChanged if the seq_num
3751 has changed */
3758 }
3765 }
3766 }
3768 /* go on with the call chain */
3770 }
3774 /*
3775 handle a rename request
3777 On a rename we need to do an extra ldb_modify which sets the
3778 whenChanged and uSNChanged attributes. We do this in a callback after the success.
3779 */
3781 {
3788 /* do not manipulate our control entries */
3791 }
3794 DSDB_CONTROL_DBCHECK_FIX_LINK_DN_NAME);
3797 }
3806 }
3818 }
3820 /* go on with the call chain */
3822 }
3824 /* After the rename is compleated, update the whenchanged etc */
3826 {
3849 }
3856 LDB_ERR_OPERATIONS_ERROR);
3857 }
3859 /* TODO:
3860 * - replace the old object with the newly constructed one
3861 */
3867 }
3878 }
3880 /* normalize the rdn attribute name */
3886 }
3894 }
3900 }
3905 }
3907 /*
3908 * here we let replmd_update_rpmd() only search for
3909 * the existing "replPropertyMetaData" and rdn_name attributes.
3910 *
3911 * We do not want the existing "name" attribute as
3912 * the "name" attribute needs to get the version
3913 * updated on rename even if the rdn value hasn't changed.
3914 *
3915 * This is the diff of the meta data, for a moved user
3916 * on a w2k8r2 server:
3917 *
3918 * # record 1
3919 * -dn: CN=sdf df,CN=Users,DC=bla,DC=base
3920 * +dn: CN=sdf df,OU=TestOU,DC=bla,DC=base
3921 * replPropertyMetaData: NDR: struct replPropertyMetaDataBlob
3922 * version : 0x00000001 (1)
3923 * reserved : 0x00000000 (0)
3924 * @@ -66,11 +66,11 @@ replPropertyMetaData: NDR: struct re
3925 * local_usn : 0x00000000000037a5 (14245)
3926 * array: struct replPropertyMetaData1
3927 * attid : DRSUAPI_ATTID_name (0x90001)
3928 * - version : 0x00000001 (1)
3929 * - originating_change_time : Wed Feb 9 17:20:49 2011 CET
3930 * + version : 0x00000002 (2)
3931 * + originating_change_time : Wed Apr 6 15:21:01 2011 CEST
3932 * originating_invocation_id: 0d36ca05-5507-4e62-aca3-354bab0d39e1
3933 * - originating_usn : 0x00000000000037a5 (14245)
3934 * - local_usn : 0x00000000000037a5 (14245)
3935 * + originating_usn : 0x0000000000003834 (14388)
3936 * + local_usn : 0x0000000000003834 (14388)
3937 * array: struct replPropertyMetaData1
3938 * attid : DRSUAPI_ATTID_userAccountControl (0x90008)
3939 * version : 0x00000004 (4)
3940 */
3954 }
3959 }
3966 }
3970 msg,
3973 req);
3978 }
3980 /* current partition control is needed by "replmd_op_callback" */
3983 DSDB_CONTROL_CURRENT_PARTITION_OID,
3988 }
3989 }
3998 }
4005 }
4007 /* go on with the call chain - do the modify after the rename */
4009 }
4011 /*
4012 * remove links from objects that point at this object when an object
4013 * is deleted. We remove it from the NEXT module per MS-DRSR 5.160
4014 * RemoveObj which states that link removal due to the object being
4015 * deleted is NOT an originating update - they just go away!
4016 *
4017 */
4027 {
4050 }
4056 }
4058 /* remove the link */
4064 }
4071 }
4080 }
4084 DSDB_FLAG_NEXT_MODULE |
4085 DSDB_SEARCH_SHOW_EXTENDED_DN |
4086 DSDB_SEARCH_SHOW_RECYCLED,
4087 parent);
4097 }
4102 }
4116 }
4118 /*
4119 * This call 'upgrades' the links in link_dns, but we
4120 * do not commit the result back into the database, so
4121 * this is safe to call in FL2000 or on databases that
4122 * have been run at that level in the past.
4123 */
4125 tmp_ctx,
4128 parent);
4132 }
4142 }
4153 }
4155 /*
4156 * If we find a backlink to ourself, we will delete
4157 * the forward link before we get to process that
4158 * properly, so just let the caller process this via
4159 * the forward link.
4160 *
4161 * We do this once we are sure we have the forward
4162 * link (to ourself) in case something is very wrong
4163 * and they are out of sync.
4164 */
4167 }
4169 /* This needs to get the Binary DN, by first searching */
4177 /*
4178 * Ensure that we tell the modification to vanish any linked
4179 * attributes (not simply mark them as isDeleted = TRUE)
4180 */
4187 }
4188 }
4191 }
4194 /*
4195 handle update of replication meta data for deletion of objects
4197 This also handles the mapping of delete to a rename operation
4198 to allow deletes to be replicated.
4200 It also handles the incoming deleted objects, to ensure they are
4201 fully deleted here. In that case re_delete is true, and we do not
4202 use this as a signal to change the deleted state, just reinforce it.
4204 */
4205 static int replmd_delete_internals(struct ldb_module *module, struct ldb_request *req, bool re_delete)
4206 {
4220 /*
4221 * This list MUST be kept in case-insensitive sorted order,
4222 * as we use it in a binary search with ldb_attr_cmp().
4223 *
4224 * We get this hard-coded list from
4225 * MS-ADTS section 3.1.1.5.5.1.1 "Tombstone Requirements".
4226 */
4268 /*
4269 * DO NOT JUST APPEND TO THIS LIST.
4270 *
4271 * In case you missed the note at the top, this list is kept
4272 * in case-insensitive sorted order. In the unlikely event you
4273 * need to add an attrbute, please add it in the RIGHT PLACE.
4274 */
4275 };
4277 DSDB_SECRET_ATTRIBUTES,
4279 NULL
4280 };
4284 };
4293 }
4295 /*
4296 * We have to allow dbcheck to remove an object that
4297 * is beyond repair, and to do so totally. This could
4298 * mean we we can get a partial object from the other
4299 * DC, causing havoc, so dbcheck suggests
4300 * re-replication first. dbcheck sets both DBCHECK
4301 * and RELAX in this situation.
4302 */
4305 /* really, really remove it */
4307 }
4313 }
4319 }
4323 /* we need the complete msg off disk, so we can work out which
4324 attributes need to be removed */
4326 DSDB_FLAG_NEXT_MODULE |
4327 DSDB_SEARCH_SHOW_RECYCLED |
4328 DSDB_SEARCH_REVEAL_INTERNALS |
4338 }
4345 /* This supports us noticing an incoming isDeleted and acting on it */
4349 }
4352 /*
4353 * We have to prevent objects being deleted, even if
4354 * the administrator really wants them gone, as
4355 * without the tombstone, we can get a partial object
4356 * from the other DC, causing havoc.
4357 *
4358 * The only other valid case is when the 180 day
4359 * timeout has expired, when relax is specified.
4360 */
4362 /* it is already deleted - really remove it this time */
4365 }
4371 }
4378 }
4385 }
4389 /* consider the SYSTEM_FLAG_DISALLOW_MOVE_ON_DELETE flag */
4390 disallow_move_on_delete =
4394 /* work out where we will be renaming this object to */
4400 /*
4401 * We should not move objects if we can't find the
4402 * deleted objects DN. Not moving (or otherwise
4403 * harming) the Deleted Objects DN itself is handled
4404 * in the caller.
4405 */
4412 }
4414 /* this is probably an attempted delete on a partition
4415 * that doesn't allow delete operations, such as the
4416 * schema partition */
4423 }
4430 }
4431 }
4433 /* get the objects GUID from the search we just did */
4440 ldb,
4441 new_dn,
4443 guid);
4448 }
4457 }
4460 /*
4461 * No matter what has happened with other renames etc, try again to
4462 * get this to be under the deleted DN. See MS-DRSR 5.160 RemoveObj
4463 */
4473 }
4484 }
4485 }
4487 /*
4488 now we need to modify the object in the following ways:
4490 - add isDeleted=TRUE
4491 - update rDN and name, with new rDN
4492 - remove linked attributes
4493 - remove objectCategory and sAMAccountType
4494 - remove attribs not on the preserved list
4495 - preserved if in above list, or is rDN
4496 - remove all linked attribs from this object
4497 - remove all links from other objects to this object
4498 (note we use the backlinks to do this, so we won't find one-way
4499 links that still point to this object, or deactivated two-way
4500 links, i.e. 'member' after the user has been removed from the
4501 group)
4502 - add lastKnownParent
4503 - update replPropertyMetaData?
4505 see MS-ADTS "Tombstone Requirements" section 3.1.1.5.5.1.1
4506 */
4513 /* we need the storage form of the parent GUID */
4516 DSDB_FLAG_NEXT_MODULE |
4517 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT |
4518 DSDB_SEARCH_REVEAL_INTERNALS|
4522 "repmd_delete: Failed to %s %s, "
4530 }
4532 /*
4533 * Now we can use the DB version,
4534 * it will have the extended DN info in it
4535 */
4538 parent_dn,
4543 }
4546 parent_dn_str);
4549 ": Failed to add lastKnownParent "
4554 }
4560 }
4567 ": Failed to add msDS-LastKnownRDN "
4572 }
4578 }
4580 }
4581 }
4588 /*
4589 * MS-ADTS 3.1.1.5.5.1.1 Tombstone Requirements
4590 * describes what must be removed from a tombstone
4591 * object
4592 *
4593 * MS-ADTS 3.1.1.5.5.1.3 Recycled-Object Requirements
4594 * describes what must be removed from a recycled
4595 * object
4596 *
4597 */
4599 /*
4600 * we also mark it as recycled, meaning this object can't be
4601 * recovered (we are stripping its attributes).
4602 * This is done only if we have this schema object of course ...
4603 * This behavior is identical to the one of Windows 2008R2 which
4604 * always set the isRecycled attribute, even if the recycle-bin is
4605 * not activated and what ever the forest level is.
4606 */
4617 }
4619 }
4623 /* work out which of the old attributes we will be removing */
4633 __location__
4634 ": Attribute %s "
4635 "not found in schema "
4636 "when deleting %s. "
4639 old_dn_str);
4642 }
4644 /* don't remove the rDN */
4646 }
4650 /*
4651 * we have a backlink in this object
4652 * that needs to be removed. We're not
4653 * allowed to remove it directly
4654 * however, so we instead setup a
4655 * modify to delete the corresponding
4656 * forward link
4657 */
4659 replmd_private,
4667 __location__
4668 ": Failed to remove backlink of "
4671 old_dn_str,
4675 }
4678 /*
4679 * now we continue, which means we
4680 * won't remove this backlink
4681 * directly
4682 */
4684 }
4686 /*
4687 * Otherwise vanish the link, we are
4688 * out of sync and the controlling
4689 * object does not have the source
4690 * link any more
4691 */
4699 }
4703 ldb_attr_cmp,
4704 attr);
4705 /*
4706 * If we are preserving, do not do the
4707 * ldb_msg_add_empty() below, continue
4708 * to the next element
4709 */
4712 }
4714 /*
4715 * Ensure that we tell the modification to vanish any linked
4716 * attributes (not simply mark them as isDeleted = TRUE)
4717 */
4719 }
4725 }
4726 }
4731 /*
4732 * MS-ADTS 3.1.1.5.5.1.2 Deleted-Object Requirements
4733 * describes what must be removed from a deleted
4734 * object
4735 */
4742 }
4749 }
4755 }
4760 /* work out what the new rdn value is, for updating the
4761 rDN and name fields */
4766 }
4772 }
4779 }
4788 }
4790 }
4791 }
4793 /*
4794 * TODO: Per MS-DRSR 5.160 RemoveObj we should remove links directly, not as an originating update!
4795 *
4796 */
4798 /*
4799 * No matter what has happned with other renames, try again to
4800 * get this to be under the deleted DN.
4801 */
4803 /* now rename onto the new DN */
4812 }
4814 }
4819 /*
4820 * This should not fail, so be quite verbose in the
4821 * error handling if it fails
4822 */
4826 "after successful rename to %s. "
4838 }
4840 tmp_ctx,
4841 LDB_CHANGETYPE_MODIFY,
4842 msg);
4847 s);
4849 "replmd_delete: Failed to modify"
4856 }
4861 }
4864 {
4866 }
4870 {
4872 }
4874 static int replmd_replicated_request_werror(struct replmd_replicated_request *ar, WERROR status)
4875 {
4877 /* TODO: do some error mapping */
4879 /* Let the caller know the full WERROR */
4883 }
4889 {
4896 }
4897 }
4899 }
4902 /*
4903 return true if an update is newer than an existing entry
4904 see section 5.11 of MS-ADTS
4905 */
4910 NTTIME current_change_time,
4911 NTTIME update_change_time)
4912 {
4915 }
4918 }
4920 }
4924 {
4931 }
4936 {
4939 /*
4940 * If the new replPropertyMetaData entry for this attribute is
4941 * not provided (this happens in the case where we look for
4942 * ATTID_name, but the name was not changed), then the local
4943 * state is clearly still current, as the remote
4944 * server didn't send it due to being older the high watermark
4945 * USN we sent.
4946 */
4949 }
4952 /*
4953 * if we compare equal then do an
4954 * update. This is used when a client
4955 * asks for a FULL_SYNC, and can be
4956 * used to recover a corrupt
4957 * replica.
4958 *
4959 * This call is a bit tricky, what we
4960 * are doing it turning the 'is_newer'
4961 * call into a 'not is older' by
4962 * swapping cur_m and new_m, and negating the
4963 * outcome.
4964 */
4966 cur_m);
4969 new_m);
4970 }
4972 }
4975 /*
4976 form a DN for a deleted (DEL:) or conflict (CNF:) DN
4977 */
4985 {
4999 }
5001 /*
5002 * TODO: Per MS-ADTS 3.1.1.5.5 Delete Operation
5003 * we should truncate this value to ensure the RDN is not more than 255 chars.
5004 *
5005 * However we MS-ADTS 3.1.1.5.1.2 Naming Constraints indicates that:
5006 *
5007 * "Naming constraints are not enforced for replicated
5008 * updates." so this is safe and we don't have to work out not
5009 * splitting a UTF8 char right now.
5010 */
5013 /*
5014 * sizeof(guid_str.buf) will always be longer than
5015 * strlen(guid_str.buf) but we allocate using this and
5016 * waste the trailing bytes to avoid scaring folks
5017 * with memcpy() using strlen() below
5018 */
5020 deleted_child_rdn_val.data
5030 }
5039 /*
5040 * talloc won't allocate more than 256MB so we can't
5041 * overflow but just to be sure
5042 */
5045 }
5054 /* Now set the value into the RDN, without parsing it */
5056 dn,
5058 rdn_name,
5059 deleted_child_rdn_val);
5062 }
5065 /*
5066 form a conflict DN
5067 */
5072 {
5082 }
5087 }
5092 rdn_name,
5093 rdn_val,
5097 }
5099 }
5101 /*
5102 form a deleted DN
5103 */
5110 {
5114 rdn_name,
5115 rdn_value,
5116 guid);
5117 }
5120 /*
5121 perform a modify operation which sets the rDN and name attributes to
5122 their current values. This has the effect of changing these
5123 attributes to have been last updated by the current DC. This is
5124 needed to ensure that renames performed as part of conflict
5125 resolution are propagated to other DCs
5126 */
5129 {
5139 }
5145 }
5147 /* normalize the rdn attribute name */
5151 }
5157 }
5161 }
5164 }
5166 /*
5167 * We have to mark this as a replicated update otherwise
5168 * schema_data may reject a rename in the schema partition
5169 */
5173 req);
5179 }
5185 failed:
5190 }
5193 /*
5194 callback for conflict DN handling where we have renamed the incoming
5195 record. After renaming it, we need to ensure the change of name and
5196 rDN for the incoming record is seen as an originating update by this DC.
5198 This also handles updating lastKnownParent for entries sent to lostAndFound
5199 */
5201 {
5208 /* call the normal callback for everything except success */
5210 }
5221 }
5223 /* perform a modify of the rDN and name of the record */
5228 }
5235 }
5240 ldb_dn_get_extended_linearized(msg, ar->objs->objects[ar->index_current].last_known_parent, 1));
5245 }
5254 }
5256 }
5259 }
5263 /*
5264 * A helper for replmd_op_possible_conflict_callback() and
5265 * replmd_replicated_handle_rename()
5266 */
5272 {
5287 ldb,
5288 "Failed to determine if we are an RODC when attempting "
5292 }
5295 /*
5296 * We are on an RODC, or were a GC for this
5297 * partition, so we have to fail this until
5298 * someone who owns the partition sorts it
5299 * out
5300 */
5302 ldb,
5303 "Conflict adding object '%s' from incoming replication "
5305 " - We must fail the operation until a master for this "
5309 }
5311 /*
5312 * first we need the replPropertyMetaData attribute from the
5313 * old record
5314 */
5316 attrs,
5317 DSDB_FLAG_NEXT_MODULE |
5318 DSDB_SEARCH_SHOW_DELETED |
5325 }
5331 ": Unable to find replPropertyMetaData for conflicting "
5335 }
5345 }
5349 /*
5350 * we decide which is newer based on the RPMD on the name
5351 * attribute. See [MS-DRSR] ResolveNameConflict.
5352 *
5353 * We expect omd_name to be present, as this is from a local
5354 * search, but while rmd_name should have been given to us by
5355 * the remote server, if it is missing we just prefer the
5356 * local name in
5357 * replmd_replPropertyMetaData1_new_should_be_taken()
5358 */
5360 DRSUAPI_ATTID_name);
5362 DRSUAPI_ATTID_name);
5365 ": Failed to find name attribute in "
5369 }
5371 /*
5372 * Should we preserve the current record, and so rename the
5373 * incoming record to be a conflict?
5374 */
5378 DSDB_REPL_FLAG_PRIORITISE_INCOMING),
5382 }
5385 /*
5386 callback for replmd_replicated_apply_add()
5387 This copes with the creation of conflict records in the case where
5388 the DN exists, but with a different objectGUID
5389 */
5390 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))
5391 {
5401 /* call the normal callback for success */
5404 }
5406 /*
5407 * we have a conflict, and need to decide if we will keep the
5408 * new record or the old record
5409 */
5414 /* For failures other than conflicts, fail the whole operation here */
5416 ldb_asprintf_errstring(ldb_module_get_ctx(ar->module), "Failed to locally apply remote add of %s: %s",
5421 LDB_ERR_OPERATIONS_ERROR);
5422 }
5429 }
5440 }
5448 }
5453 /* re-submit the request, but with the new DN */
5457 /* we are renaming the existing record */
5466 }
5475 }
5488 }
5490 /*
5491 * now we need to ensure that the rename is seen as an
5492 * originating update. We do that with a modify.
5493 */
5497 }
5499 DEBUG(2,(__location__ ": With conflicting record renamed, re-apply replicated creation of '%s'\n",
5501 }
5505 req,
5506 msg,
5508 ar,
5509 callback,
5510 req);
5513 }
5516 /* current partition control needed by "repmd_op_callback" */
5518 DSDB_CONTROL_CURRENT_PARTITION_OID,
5522 }
5525 /* this tells the partition module to make it a
5526 partial replica if creating an NC */
5528 DSDB_CONTROL_PARTIAL_REPLICA,
5532 }
5533 }
5535 /*
5536 * Finally we re-run the add, otherwise the new record won't
5537 * exist, as we are here because of that exact failure!
5538 */
5540 failed:
5542 /* on failure make the caller get the error. This means
5543 * replication will stop with an error, but there is not much
5544 * else we can do.
5545 */
5548 }
5550 ret);
5551 }
5553 /*
5554 callback for replmd_replicated_apply_add()
5555 This copes with the creation of conflict records in the case where
5556 the DN exists, but with a different objectGUID
5557 */
5559 {
5564 /* This is like a conflict DN, where we put the object in LostAndFound
5565 see MS-DRSR 4.1.10.6.10 FindBestParentObject */
5567 }
5570 }
5572 /*
5573 this is called when a new object comes in over DRS
5574 */
5576 {
5587 NTTIME now;
5603 }
5610 }
5612 ret = ldb_msg_add_string(msg, "whenChanged", ar->objs->objects[ar->index_current].when_changed);
5615 }
5620 }
5625 }
5627 /* remove any message elements that have zero values */
5637 }
5642 i--;
5644 }
5645 }
5651 LDB_CHANGETYPE_ADD,
5652 msg);
5655 s));
5662 }
5666 /*
5667 * the meta data array is already sorted by the caller, except
5668 * for the RDN, which needs to be added.
5669 */
5677 ldb_asprintf_errstring(ldb, "%s: error during DRS repl ADD: %s", __func__, ldb_errstring(ldb));
5679 }
5683 ldb_asprintf_errstring(ldb, "%s: error during DRS repl ADD: %s", __func__, ldb_errstring(ldb));
5685 }
5689 }
5695 }
5699 }
5704 /*
5705 * Ensure any local ACL inheritence is applied from
5706 * the parent object.
5707 *
5708 * This is needed because descriptor is above
5709 * repl_meta_data in the module stack, so this will
5710 * not be trigered 'naturally' by the flow of
5711 * operations.
5712 */
5722 }
5723 }
5728 ldb,
5729 ar,
5730 msg,
5732 ar,
5733 replmd_op_add_callback,
5738 /* current partition control needed by "repmd_op_callback" */
5740 DSDB_CONTROL_CURRENT_PARTITION_OID,
5745 /* this tells the partition module to make it a
5746 partial replica if creating an NC */
5748 DSDB_CONTROL_PARTIAL_REPLICA,
5751 }
5754 }
5758 {
5765 LDB_ERR_OPERATIONS_ERROR);
5766 }
5768 /*
5769 * The error NO_SUCH_OBJECT is not expected, unless the search
5770 * base is the partition DN, and that case doesn't happen here
5771 * because then we wouldn't get a parent_guid_value in any
5772 * case.
5773 */
5777 }
5781 {
5789 /* Per MS-DRSR 4.1.10.6.10
5790 * FindBestParentObject we need to move this
5791 * new object under a deleted object to
5792 * lost-and-found */
5798 "No suitable NC root found for %s. "
5799 "We need to move this object because parent object %s "
5806 "Unable to find NC root for %s: %s. "
5807 "We need to move this object because parent object %s "
5813 }
5816 nc_root,
5817 DS_GUID_LOSTANDFOUND_CONTAINER,
5821 "Unable to find LostAndFound Container for %s "
5822 "in partition %s: %s. "
5823 "We need to move this object because parent object %s "
5829 }
5834 parent_dn
5837 }
5845 }
5846 }
5850 }
5852 }
5854 /* we ignore referrals */
5871 }
5873 /*
5874 * This error code is really important, as it
5875 * is the flag back to the callers to retry
5876 * this with DRSUAPI_DRS_GET_ANC, and so get
5877 * the parent objects before the child
5878 * objects
5879 */
5882 }
5888 }
5891 }
5892 }
5896 }
5898 /*
5899 * Look for the parent object, so we put the new object in the right
5900 * place This is akin to NameObject in MS-DRSR - this routine and the
5901 * callbacks find the right parent name, and correct name for this
5902 * object
5903 */
5906 {
5922 }
5923 }
5932 ldb,
5933 ar,
5935 LDB_SCOPE_SUBTREE,
5936 filter,
5937 attrs,
5938 NULL,
5939 ar,
5940 replmd_replicated_apply_search_for_parent_callback,
5945 DSDB_SEARCH_SHOW_RECYCLED|
5946 DSDB_SEARCH_SHOW_DELETED|
5947 DSDB_SEARCH_SHOW_EXTENDED_DN);
5950 }
5953 }
5955 /*
5956 handle renames that come in over DRS replication
5957 */
5962 {
5981 }
5985 ldb_asprintf_errstring(ldb_module_get_ctx(ar->module), "Failed to locally apply remote rename from %s to %s: %s",
5990 }
5999 }
6014 }
6027 }
6033 }
6035 /* we are renaming the existing record */
6042 }
6051 }
6064 }
6066 /*
6067 * now we need to ensure that the rename is seen as an
6068 * originating update. We do that with a modify.
6069 */
6073 }
6075 DEBUG(2,(__location__ ": With conflicting record renamed, re-apply replicated rename '%s' -> '%s'\n",
6079 /*
6080 * With the other record out of the way, do the rename we had
6081 * at the top again
6082 */
6091 }
6095 failed:
6096 /*
6097 * On failure make the caller get the error
6098 * This means replication will stop with an error,
6099 * but there is not much else we can do. In the
6100 * LDB_ERR_ENTRY_ALREADY_EXISTS case this is exactly what is
6101 * needed.
6102 */
6105 }
6109 }
6113 {
6137 NTSTATUS nt_status;
6142 NTTIME now;
6155 /* find existing meta data */
6163 }
6167 }
6168 }
6179 s,
6187 rmd)));
6196 }
6203 /*
6204 * Fill in the remote_parent_guid with the GUID or an all-zero
6205 * GUID.
6206 */
6211 }
6213 /*
6214 * To ensure we follow a complex rename chain around, we have
6215 * to confirm that the DN is the same (mostly to confirm the
6216 * RDN) and the parentGUID is the same.
6217 *
6218 * This ensures we keep things under the correct parent, which
6219 * replmd_replicated_handle_rename() will do.
6220 */
6226 /*
6227 * handle renames, even just by case that come in over
6228 * DRS. Changes in the parent DN don't hit us here,
6229 * because the search for a parent will clean up those
6230 * components.
6231 *
6232 * We also have already filtered out the case where
6233 * the peer has an older name to what we have (see
6234 * replmd_replicated_apply_search_callback())
6235 */
6238 /*
6239 * This looks strange, but we must set this after any
6240 * rename, otherwise the SD propegation will not
6241 * happen (which might matter if we have a new parent)
6242 *
6243 * The additional case of calling
6244 * replmd_op_name_modify_callback (below) is
6245 * controlled by renamed_to_conflict.
6246 */
6248 }
6257 }
6260 /*
6261 * Set the callback to one that will fix up the name
6262 * metadata on the new conflict DN
6263 */
6265 }
6275 /* first copy the old meta data */
6278 ni++;
6279 }
6282 /* now merge in the new meta data */
6291 }
6298 /* replace the entry */
6304 }
6305 }
6316 }
6319 }
6326 }
6328 /* we don't want to apply this change so remove the attribute */
6330 removed_attrs++;
6334 }
6343 }
6344 }
6355 }
6356 ni++;
6357 }
6359 /*
6360 * finally correct the size of the meta_data array
6361 */
6372 ldb_asprintf_errstring(ldb, "%s: error during DRS repl merge: %s", __func__, ldb_errstring(ldb));
6374 }
6375 }
6376 /*
6377 * sort the new meta data array
6378 */
6381 ldb_asprintf_errstring(ldb, "%s: error during DRS repl merge: %s", __func__, ldb_errstring(ldb));
6383 }
6385 /*
6386 * Work out if this object is deleted, so we can prune any extra attributes. See MS-DRSR 4.1.10.6.9
6387 * UpdateObject.
6388 *
6389 * This also controls SD propagation below
6390 */
6395 }
6399 /*
6400 * check if some replicated attributes left, otherwise skip the ldb_modify() call
6401 */
6407 }
6413 /*
6414 * This is an new name for this object, so we must
6415 * inherit from the parent
6416 *
6417 * This is needed because descriptor is above
6418 * repl_meta_data in the module stack, so this will
6419 * not be trigered 'naturally' by the flow of
6420 * operations.
6421 */
6431 }
6432 }
6435 /*
6436 * This is an existing object, so there is no need to
6437 * inherit from the parent, but we must inherit any
6438 * incoming changes to our child objects.
6439 *
6440 * This is needed because descriptor is above
6441 * repl_meta_data in the module stack, so this will
6442 * not be trigered 'naturally' by the flow of
6443 * operations.
6444 */
6454 }
6455 }
6457 /* create the meta data value */
6463 }
6465 /*
6466 * when we know that we'll modify the record, add the whenChanged, uSNChanged
6467 * and replPopertyMetaData attributes
6468 */
6469 ret = ldb_msg_add_string(msg, "whenChanged", ar->objs->objects[ar->index_current].when_changed);
6472 }
6476 }
6480 }
6484 /* we want to replace the old values */
6493 }
6494 }
6495 }
6501 LDB_CHANGETYPE_MODIFY,
6502 msg);
6506 s));
6515 }
6518 ldb,
6519 ar,
6520 msg,
6522 ar,
6523 callback,
6528 /* current partition control needed by "repmd_op_callback" */
6530 DSDB_CONTROL_CURRENT_PARTITION_OID,
6535 }
6539 {
6546 LDB_ERR_OPERATIONS_ERROR);
6547 }
6552 }
6560 /* we ignore referrals */
6564 {
6576 /*
6577 * This is the ADD case, find the appropriate parent,
6578 * as this object doesn't exist locally:
6579 */
6584 }
6587 }
6589 /*
6590 * Otherwise, in the MERGE case, work out if we are
6591 * attempting a rename, and if so find the parent the
6592 * newly renamed object wants to belong under (which
6593 * may not be the parent in it's attached string DN
6594 */
6599 /* find existing meta data */
6608 }
6612 }
6613 }
6621 "as local object has an all-zero parentGUID attribute, "
6625 }
6627 /*
6628 * now we need to check for double renames. We could have a
6629 * local rename pending which our replication partner hasn't
6630 * received yet. We choose which one wins by looking at the
6631 * attribute stamps on the two objects, the newer one wins.
6632 *
6633 * This also simply applies the correct algorithms for
6634 * determining if a change was made to name at all, or
6635 * if the object has just been renamed under the same
6636 * parent.
6637 */
6641 DEBUG(0,(__location__ ": Failed to find name attribute in local LDB replPropertyMetaData for %s\n",
6644 }
6646 /*
6647 * if there is no name attribute given then we have to assume the
6648 * object we've received has the older name
6649 */
6657 /* Merge on the existing object, with rename */
6672 /*
6673 * Merge on the existing object, force no
6674 * rename (code below just to explain why in
6675 * the DEBUG() logs)
6676 */
6690 }
6699 }
6700 /*
6701 * This assignment ensures that the strcmp()
6702 * and GUID_equal() calls in
6703 * replmd_replicated_apply_merge() avoids the
6704 * rename call
6705 */
6711 }
6714 }
6715 }
6716 }
6720 }
6722 /**
6723 * Returns true if we can group together processing this link attribute,
6724 * i.e. it has the same source-object and attribute ID as other links
6725 * already in the group
6726 */
6729 {
6735 }
6737 /**
6738 * Creates a new la_entry to store replication info for a single
6739 * linked attribute.
6740 */
6745 {
6750 }
6754 }
6760 }
6764 /*
6765 * we need to steal the non-scalars so they stay
6766 * around until the end of the transaction
6767 */
6772 }
6774 /**
6775 * Stores the linked attributes received in the replication chunk - these get
6776 * applied at the end of the transaction. We also check that each linked
6777 * attribute is valid, i.e. source and target objects are known.
6778 */
6780 {
6796 /* save away the linked attributes for the end of the transaction */
6801 /* create an entry to store the received link attribute info */
6808 }
6810 /*
6811 * check if we're still dealing with the same source object
6812 * as the last link
6813 */
6819 /* get a new mem_ctx to lookup the source object */
6825 }
6827 /* verify the link source exists */
6832 /*
6833 * When we fail to find the source object, the error
6834 * code we pass back here is really important. It flags
6835 * back to the callers to retry this request with
6836 * DRSUAPI_DRS_GET_ANC. This case should never happen
6837 * if we're replicating from a Samba DC, but it is
6838 * needed to talk to a Windows DC
6839 */
6843 err);
6845 }
6846 }
6852 }
6854 /* group the links together by source-object for efficiency */
6861 }
6863 }
6866 }
6870 }
6875 {
6889 /*
6890 * Now that we've applied all the objects, check the new linked
6891 * attributes and store them (we apply them in .prepare_commit)
6892 */
6897 }
6899 /* done applying objects, move on to the next stage */
6901 }
6914 ldb,
6915 ar,
6917 LDB_SCOPE_SUBTREE,
6918 filter,
6919 attrs,
6920 NULL,
6921 ar,
6922 replmd_replicated_apply_search_callback,
6926 /*
6927 * We set DSDB_SEARCH_SHOW_EXTENDED_DN to get the GUID on the
6928 * DN. This in turn helps our operational module find the
6929 * record by GUID, not DN lookup which is more error prone if
6930 * DN indexing changes. We prefer to keep chasing GUIDs
6931 * around if possible, even within a transaction.
6932 *
6933 * The aim here is to keep replication moving and allow a
6934 * reindex later.
6935 */
6941 }
6944 }
6946 /*
6947 * Returns true if we need to do extra processing to handle deleted object
6948 * changes received via replication
6949 */
6952 {
6958 /* not a deleted object, so don't set isDeleted */
6960 }
6966 /*
6967 * if the Deleted Object container lookup failed, then just apply
6968 * isDeleted (note that it doesn't exist for the Schema partition)
6969 */
6972 }
6974 /*
6975 * the Deleted Objects container has isDeleted set but is not entirely
6976 * a deleted object, so DON'T re-apply isDeleted to it
6977 */
6980 }
6983 }
6985 /*
6986 * This is essentially a wrapper for replmd_replicated_apply_next()
6987 *
6988 * This is needed to ensure that both codepaths call this handler.
6989 */
6991 {
7003 /* nothing to do */
7006 }
7008 /*
7009 * Do a delete here again, so that if there is
7010 * anything local that conflicts with this
7011 * object being deleted, it is removed. This
7012 * includes links. See MS-DRSR 4.1.10.6.9
7013 * UpdateObject.
7014 *
7015 * If the object is already deleted, and there
7016 * is no more work required, it doesn't do
7017 * anything.
7018 */
7020 /* This has been updated to point to the DN we eventually did the modify on */
7026 }
7033 }
7035 /* Build a delete request, which hopefully will artually turn into nothing */
7038 NULL,
7039 res,
7040 ldb_modify_default_callback,
7046 }
7048 /*
7049 * This is the guts of the call, call back
7050 * into our delete code, but setting the
7051 * re_delete flag so we delete anything that
7052 * shouldn't be there on a deleted or recycled
7053 * object
7054 */
7058 }
7063 }
7067 }
7071 {
7079 LDB_ERR_OPERATIONS_ERROR);
7080 }
7084 }
7089 LDB_ERR_OPERATIONS_ERROR);
7090 }
7095 }
7098 {
7117 NTTIME now;
7131 /* this happens for a REPL_OBJ call where we are
7132 creating the target object by replicating it. The
7133 subdomain join code does this for the partition DN
7134 */
7137 }
7144 }
7146 /*
7147 * first create the new replUpToDateVector
7148 */
7156 }
7160 }
7161 }
7163 /*
7164 * the new uptodateness vector will at least
7165 * contain 1 entry, one for the source_dsa
7166 *
7167 * plus optional values from our old vector and the one from the source_dsa
7168 */
7174 if (!nuv.ctr.ctr2.cursors) return replmd_replicated_request_werror(ar, WERR_NOT_ENOUGH_MEMORY);
7176 /* first copy the old vector */
7179 ni++;
7180 }
7182 /* merge in the source_dsa vector is available */
7189 }
7195 }
7201 }
7203 }
7207 /* if it's not there yet, add it */
7209 ni++;
7210 }
7212 /*
7213 * finally correct the size of the cursors array
7214 */
7217 /*
7218 * sort the cursors
7219 */
7222 /*
7223 * create the change ldb_message
7224 */
7234 }
7238 }
7241 /*
7242 * now create the new repsFrom value from the given repsFromTo1 structure
7243 */
7251 /*
7252 * first see if we already have a repsFrom value for the current source dsa
7253 * if so we'll later replace this value
7254 */
7268 }
7272 }
7274 /*
7275 * we compare the source dsa objectGUID not the invocation_id
7276 * because we want only one repsFrom value per source dsa
7277 * and when the invocation_id of the source dsa has changed we don't need
7278 * the old repsFrom with the old invocation_id
7279 */
7284 }
7289 }
7291 /*
7292 * copy over all old values to the new ldb_message
7293 */
7297 }
7299 /*
7300 * if we haven't found an old repsFrom value for the current source dsa
7301 * we'll add a new value
7302 */
7310 }
7312 /* we now fill the value which is already attached to ldb_message */
7319 }
7321 /*
7322 * the ldb_message_element for the attribute, has all the old values and the new one
7323 * so we'll replace the whole attribute with all values
7324 */
7329 LDB_CHANGETYPE_MODIFY,
7330 msg);
7333 }
7335 /* prepare the ldb_modify() request */
7337 ldb,
7338 ar,
7339 msg,
7341 ar,
7342 replmd_replicated_uptodate_modify_callback,
7348 }
7352 {
7359 LDB_ERR_OPERATIONS_ERROR);
7360 }
7365 }
7373 /* we ignore referrals */
7380 }
7381 }
7385 }
7389 {
7399 NULL
7400 };
7405 /*
7406 * Let the caller know that we did an originating updates
7407 */
7411 ldb,
7412 ar,
7414 LDB_SCOPE_BASE,
7416 attrs,
7417 NULL,
7418 ar,
7419 replmd_replicated_uptodate_search_callback,
7425 }
7429 static int replmd_extended_replicated_objects(struct ldb_module *module, struct ldb_request *req)
7430 {
7443 ldb_debug(ldb, LDB_DEBUG_FATAL, "replmd_extended_replicated_objects: invalid extended data\n");
7445 }
7448 ldb_debug(ldb, LDB_DEBUG_FATAL, "replmd_extended_replicated_objects: extended data invalid version [%u != %u]\n",
7451 }
7457 /* Set the flags to have the replmd_op_callback run over the full set of objects */
7466 }
7474 }
7479 }
7481 /* If this change contained linked attributes in the body
7482 * (rather than in the links section) we need to update
7483 * backlinks in linked_attributes */
7487 }
7493 }
7495 /**
7496 * Checks how to handle an missing target - either we need to fail the
7497 * replication and retry with GET_TGT, ignore the link and continue, or try to
7498 * add a partial link to an unknown target.
7499 */
7509 {
7513 /*
7514 * we may not be able to resolve link targets properly when
7515 * dealing with subsets of objects, e.g. the source is a
7516 * critical object and the target isn't
7517 *
7518 * TODO:
7519 * When we implement Trusted Domains we need to consider
7520 * whether they get treated as an incomplete replica here or not
7521 */
7524 /*
7525 * Ignore the link. We don't increase the highwater-mark in
7526 * the object subset cases, so subsequent replications should
7527 * resolve any missing links
7528 */
7534 }
7537 mem_ctx,
7538 source_dn,
7539 target_dn);
7541 /*
7542 * We allow the join.py code to point out that all
7543 * replication is completed, so failing now would just
7544 * trigger errors, rather than trigger a GET_TGT
7545 */
7548 DSDB_FULL_JOIN_REPLICATION_COMPLETED_OPAQUE_NAME),
7552 /*
7553 * if the target is already be up-to-date there's no point in
7554 * retrying. This could be due to bad timing, or if a target
7555 * on a one-way link was deleted. We ignore the link rather
7556 * than failing the replication cycle completely
7557 */
7566 }
7568 /* otherwise fail the replication and retry with GET_TGT */
7570 missing_str,
7575 }
7577 /*
7578 * The target of the cross-partition link is missing. Continue
7579 * and try to at least add the forward-link. This isn't great,
7580 * but a partial link can be fixed by dbcheck, so it's better
7581 * than dropping the link completely.
7582 */
7587 /*
7588 * Only log this when we're actually committing the objects.
7589 * This avoids spurious logs, i.e. if we're just verifying the
7590 * received link during a join.
7591 */
7595 }
7598 }
7600 /**
7601 * Checks that the target object for a linked attribute exists.
7602 * @param guid returns the target object's GUID (is returned)if it exists)
7603 * @param ignore_link set to true if the linked attribute should be ignored
7604 * (i.e. the target doesn't exist, but that it's OK to skip the link)
7605 */
7613 {
7619 NTSTATUS ntstatus;
7629 /*
7630 * This strange behaviour (allowing a NULL/missing
7631 * GUID) originally comes from:
7632 *
7633 * commit e3054ce0fe0f8f62d2f5b2a77893e7a1479128bd
7634 * Author: Andrew Tridgell <tridge@samba.org>
7635 * Date: Mon Dec 21 21:21:55 2009 +1100
7636 *
7637 * s4-drs: cope better with NULL GUIDS from DRS
7638 *
7639 * It is valid to get a NULL GUID over DRS for a deleted forward link. We
7640 * need to match by DN if possible when seeing if we should update an
7641 * existing link.
7642 *
7643 * Pair-Programmed-With: Andrew Bartlett <abartlet@samba.org>
7644 */
7647 DSDB_FLAG_NEXT_MODULE |
7648 DSDB_SEARCH_SHOW_RECYCLED |
7649 DSDB_SEARCH_SEARCH_ALL_PARTITIONS |
7650 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT,
7651 NULL);
7653 ldb_asprintf_errstring(ldb, "Failed to find GUID in linked attribute 0x%x blob for %s from %s",
7662 attrs,
7663 DSDB_FLAG_NEXT_MODULE |
7664 DSDB_SEARCH_SHOW_RECYCLED |
7665 DSDB_SEARCH_SEARCH_ALL_PARTITIONS |
7666 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT,
7667 NULL,
7670 }
7678 }
7682 /*
7683 * target object is unknown. Check whether to ignore the link,
7684 * fail the replication, or add a partial link
7685 */
7700 /* Get the object's state (i.e. Not Deleted, Tombstone, etc) */
7704 /*
7705 * Check for deleted objects as per MS-DRSR 4.1.10.6.14
7706 * ProcessLinkValue(). Link updates should not be sent for
7707 * recycled and tombstone objects (deleting the links should
7708 * happen when we delete the object). This probably means our
7709 * copy of the target object isn't up to date.
7710 */
7713 /*
7714 * target object is deleted. Check whether to ignore the
7715 * link, fail the replication, or add a partial link
7716 */
7722 }
7723 }
7727 }
7729 /**
7730 * Extracts the key details about the source object for a
7731 * linked-attribute entry.
7732 * This returns the following details:
7733 * @param ret_attr the schema details for the linked attribute
7734 * @param source_msg the search result for the source object
7735 */
7741 {
7750 /*
7751 linked_attributes[0]:
7752 &objs->linked_attributes[i]: struct drsuapi_DsReplicaLinkedAttribute
7753 identifier : *
7754 identifier: struct drsuapi_DsReplicaObjectIdentifier
7755 __ndr_size : 0x0000003a (58)
7756 __ndr_size_sid : 0x00000000 (0)
7757 guid : 8e95b6a9-13dd-4158-89db-3220a5be5cc7
7758 sid : S-0-0
7759 __ndr_size_dn : 0x00000000 (0)
7760 dn : ''
7761 attid : DRSUAPI_ATTID_member (0x1F)
7762 value: struct drsuapi_DsAttributeValue
7763 __ndr_size : 0x0000007e (126)
7764 blob : *
7765 blob : DATA_BLOB length=126
7766 flags : 0x00000001 (1)
7767 1: DRSUAPI_DS_LINKED_ATTRIBUTE_FLAG_ACTIVE
7768 originating_add_time : Wed Sep 2 22:20:01 2009 EST
7769 meta_data: struct drsuapi_DsReplicaMetaData
7770 version : 0x00000015 (21)
7771 originating_change_time : Wed Sep 2 23:39:07 2009 EST
7772 originating_invocation_id: 794640f3-18cf-40ee-a211-a93992b67a64
7773 originating_usn : 0x000000000001e19c (123292)
7775 (for cases where the link is to a normal DN)
7776 &target: struct drsuapi_DsReplicaObjectIdentifier3
7777 __ndr_size : 0x0000007e (126)
7778 __ndr_size_sid : 0x0000001c (28)
7779 guid : 7639e594-db75-4086-b0d4-67890ae46031
7780 sid : S-1-5-21-2848215498-2472035911-1947525656-19924
7781 __ndr_size_dn : 0x00000022 (34)
7782 dn : 'CN=UOne,OU=TestOU,DC=vsofs8,DC=com'
7783 */
7785 /* find the attribute being modified */
7794 }
7796 /*
7797 * All attributes listed here must be dealt with in some way
7798 * by replmd_process_linked_attribute() otherwise in the case
7799 * of isDeleted: FALSE the modify will fail with:
7800 *
7801 * Failed to apply linked attribute change 'attribute 'isDeleted':
7802 * invalid modify flags on
7803 * 'CN=g1_1527570609273,CN=Users,DC=samba,DC=example,DC=com':
7804 * 0x0'
7805 *
7806 * This is becaue isDeleted is a Boolean, so FALSE is a
7807 * legitimate value (set by Samba's deletetest.py)
7808 */
7814 /*
7815 * get the existing message from the db for the object with
7816 * this GUID, returning attribute being modified. We will then
7817 * use this msg as the basis for a modify call
7818 */
7820 DSDB_FLAG_NEXT_MODULE |
7821 DSDB_SEARCH_SEARCH_ALL_PARTITIONS |
7822 DSDB_SEARCH_SHOW_RECYCLED |
7823 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT |
7824 DSDB_SEARCH_REVEAL_INTERNALS,
7825 NULL,
7829 }
7834 }
7840 }
7842 /**
7843 * Verifies the target object is known for a linked attribute
7844 */
7850 {
7856 WERROR status;
7861 /* the value blob for the attribute holds the target object DN */
7870 }
7872 /*
7873 * We can skip the target object checks if we're only syncing critical
7874 * objects, or we know the target is up-to-date. If either case, we
7875 * still continue even if the target doesn't exist
7876 */
7882 }
7884 /*
7885 * When we fail to find the target object, the error code we pass
7886 * back here is really important. It flags back to the callers to
7887 * retry this request with DRSUAPI_DRS_GET_TGT
7888 */
7891 }
7894 }
7896 /**
7897 * Finds the current active Parsed-DN value for a single-valued linked
7898 * attribute, if one exists.
7899 * @param ret_pdn assigned the active Parsed-DN, or NULL if none was found
7900 * @returns LDB_SUCCESS (regardless of whether a match was found), unless
7901 * an error occurred
7902 */
7909 {
7916 /* nothing to do for multi-valued linked attributes */
7918 }
7924 /* skip any inactive links */
7927 }
7929 /* we've found an active value for this attribute */
7937 }
7940 }
7942 /* no active link found */
7944 }
7946 /**
7947 * @returns true if the replication linked attribute info is newer than we
7948 * already have in our DB
7949 * @param pdn the existing linked attribute info in our DB
7950 * @param la the new linked attribute info received during replication
7951 */
7954 {
7955 /* see if this update is newer than what we have already */
7962 /* no existing info so update is newer */
7964 }
7972 version,
7974 change_time,
7976 }
7978 /**
7979 * Marks an existing linked attribute value as deleted in the DB
7980 * @param pdn the parsed-DN of the target-value to delete
7981 */
7993 {
7996 NTTIME now;
8006 }
8008 /* if the existing link is active, remove its backlink */
8011 /*
8012 * NOTE WELL: After this we will never (at runtime) be
8013 * able to find this forward link (for instant
8014 * removal) if/when the link target is deleted.
8015 *
8016 * We have dbcheck rules to cover this and cope otherwise
8017 * by filtering at runtime (i.e. in the extended_dn module).
8018 */
8024 }
8025 }
8027 /* mark the existing value as deleted */
8032 }
8034 /**
8035 * Checks for a conflict in single-valued link attributes, and tries to
8036 * resolve the problem if possible.
8037 *
8038 * Single-valued links should only ever have one active value. If we already
8039 * have an active link value, and during replication we receive an active link
8040 * value for a different target DN, then we need to resolve this inconsistency
8041 * and determine which value should be active. If the received info is better/
8042 * newer than the existing link attribute, then we need to set our existing
8043 * link as deleted. If the received info is worse/older, then we should continue
8044 * to add it, but set it as an inactive link.
8045 *
8046 * Note that this is a corner-case that is unlikely to happen (but if it does
8047 * happen, we don't want it to break replication completely).
8048 *
8049 * @param pdn_being_modified the parsed DN corresponding to the received link
8050 * target (note this is NULL if the link does not already exist in our DB)
8051 * @param pdn_list all the source object's Parsed-DNs for this attribute, i.e.
8052 * any existing active or inactive values for the attribute in our DB.
8053 * @param dsdb_dn the target DN for the received link attribute
8054 * @param add_as_inactive gets set to true if the received link is worse than
8055 * the existing link - it should still be added, but as an inactive link.
8056 */
8070 {
8075 /*
8076 * check if there's a conflict for single-valued links, i.e. an active
8077 * linked attribute already exists, but it has a different target value
8078 */
8085 }
8087 /*
8088 * If no active value exists (or the received info is for the currently
8089 * active value), then no conflict exists
8090 */
8093 }
8098 /* Work out how to resolve the conflict based on which info is better */
8106 /*
8107 * Delete our existing active link. The received info will then
8108 * be added (through normal link processing) as the active value
8109 */
8118 }
8124 /*
8125 * we want to keep our existing active link and add the
8126 * received link as inactive
8127 */
8129 }
8132 }
8134 /**
8135 * Processes one linked attribute received via replication.
8136 * @param src_dn the DN of the source object for the link
8137 * @param attr schema info for the linked attribute
8138 * @param la_entry the linked attribute info received via DRS
8139 * @param element_ctx mem context for msg->element[] (when adding a new value
8140 * we need to realloc old_el->values)
8141 * @param old_el the corresponding msg->element[] for the linked attribute
8142 * @param pdn_list a (binary-searchable) parsed DN array for the existing link
8143 * values in the msg. E.g. for a group, this is the existing members.
8144 * @param change what got modified: either nothing, an existing link value was
8145 * modified, or a new link value was added.
8146 * @returns LDB_SUCCESS if OK, an error otherwise
8147 */
8159 {
8173 WERROR status;
8177 /* the value blob for the attribute holds the target object DN */
8186 }
8193 }
8195 /*
8196 * there are some cases where the target object doesn't exist, but it's
8197 * OK to ignore the linked attribute
8198 */
8201 }
8203 /* see if this link already exists */
8213 }
8220 }
8222 /* get a seq_num for this change */
8226 }
8228 /*
8229 * check for single-valued link conflicts, i.e. an active linked
8230 * attribute already exists, but it has a different target value
8231 */
8237 seq_num,
8241 }
8242 }
8248 /* remove the existing backlink */
8250 schema,
8251 src_dn,
8253 parent);
8256 }
8257 }
8266 /*
8267 * We know where the new one needs to be, from the *next
8268 * pointer into pdn_list.
8269 */
8278 }
8279 }
8283 }
8284 }
8291 }
8296 }
8303 }
8305 /* set the link attribute's value to the info that was received */
8314 }
8318 /* Set the new link as inactive/deleted to avoid conflicts */
8322 val_to_update);
8326 }
8330 /* if the new link is active, then add the new backlink */
8332 schema,
8333 src_dn,
8335 parent);
8338 }
8339 }
8344 }
8349 }
8352 {
8355 }
8358 }
8361 /*
8362 we hook into the transaction operations to allow us to
8363 perform the linked attribute updates at the end of the whole
8364 transaction. This allows a forward linked attribute to be created
8365 before the object is created. During a vampire, w2k8 sends us linked
8366 attributes before the objects they are part of.
8367 */
8369 {
8370 /* create our private structure for this transaction */
8375 /* free any leftover mod_usn records from cancelled
8376 transactions */
8381 }
8386 }
8388 /**
8389 * Processes a group of linked attributes that apply to the same source-object
8390 * and attribute-ID (and were received in the same replication chunk).
8391 */
8395 {
8407 replmd_link_changed change_type;
8415 }
8417 /*
8418 * get the attribute being modified and the search result for the
8419 * source object
8420 */
8426 }
8428 /*
8429 * Check for deleted objects per MS-DRSR 4.1.10.6.14
8430 * ProcessLinkValue, because link updates are not applied to
8431 * recycled and tombstone objects. We don't have to delete
8432 * any existing link, that should have happened when the
8433 * object deletion was replicated or initiated.
8434 *
8435 * This needs isDeleted and isRecycled to be included as
8436 * attributes in the search and so in msg if set.
8437 */
8443 }
8445 /*
8446 * Now that we know the deletion_state, remove the extra
8447 * attributes added for that purpose. We need to do this
8448 * otherwise in the case of isDeleted: FALSE the modify will
8449 * fail with:
8450 *
8451 * Failed to apply linked attribute change 'attribute 'isDeleted':
8452 * invalid modify flags on
8453 * 'CN=g1_1527570609273,CN=Users,DC=samba,DC=example,DC=com':
8454 * 0x0'
8455 *
8456 * This is becaue isDeleted is a Boolean, so FALSE is a
8457 * legitimate value (set by Samba's deletetest.py)
8458 */
8462 /* get the msg->element[] for the link attribute being processed */
8470 }
8473 }
8475 /*
8476 * go through and process the link target value(s) for this particular
8477 * source object and attribute. For optimization, the same msg is used
8478 * across multiple calls to replmd_process_linked_attribute().
8479 * Note that we should not add or remove any msg attributes inside the
8480 * loop (we should only add/modify *values* for the attribute being
8481 * processed). Otherwise msg->elements is realloc'd and old_el/pdn_list
8482 * pointers will be invalidated
8483 */
8488 /*
8489 * parse the existing links (this can be costly for a large
8490 * group, so we try to minimize the times we do it)
8491 */
8494 replmd_private,
8498 NULL);
8502 }
8503 }
8505 replmd_private,
8512 }
8514 /*
8515 * Adding a link reallocs memory, and so invalidates all the
8516 * pointers in pdn_list. Reparse the PDNs on the next loop
8517 */
8520 }
8523 num_changes++;
8524 }
8530 }
8531 }
8533 /*
8534 * it's possible we're already up-to-date and so don't need to modify
8535 * the object at all (e.g. doing a 'drs replicate --full-sync')
8536 */
8540 }
8542 /*
8543 * Note that adding the whenChanged/etc attributes below will realloc
8544 * msg->elements, invalidating the existing element/parsed-DN pointers
8545 */
8549 /* update whenChanged/uSNChanged as the object has changed */
8555 }
8561 }
8567 }
8569 /* apply the link changes to the source object */
8573 "Failed to apply linked attribute change "
8580 }
8584 }
8586 /*
8587 on prepare commit we loop over our queued la_context structures and
8588 apply each of them
8589 */
8591 {
8599 }
8601 /*
8602 * Walk the list of linked attributes from DRS replication.
8603 *
8604 * We walk backwards, to do the first entry first, as we
8605 * added the entries with DLIST_ADD() which puts them at the
8606 * start of the list
8607 *
8608 * Links are grouped together so we process links for the same
8609 * source object in one go.
8610 */
8618 la_group);
8622 }
8623 }
8627 /* possibly change @REPLCHANGED */
8631 }
8634 }
8637 {
8643 }
8657 };
8660 {
8663 }