in case there is an idmap configuration with an idmap backend that is not loadable, it is silently ignored and the default idmap backend is used instead, example: idmap config * : backend = tdb idmap config * : range = 5000-9999 idmap config WINDOM1 : backend = rids ## notice the intended typo here! idmap config WINDOM1 : range = 100000 - 999999 testing the idmaping for the WINDOM1 admin user's SID: # wbinfo --sid-to-uid S-1-5-21-1667447555-3923921447-739949389-500 5000 [2026/03/03 10:41:25.876790, 5, traceid=3] ../../lib/util/modules.c:49(load_module) Error loading module '/usr/local/samba-4.23.5-2/lib/idmap/rids.so': 0509-022 Cannot load module /usr/local/samba-4.23.5-2/lib/idmap/rid s.so. 0509-026 System error: A file or directory in the path name does not exist. [2026/03/03 10:41:25.877463, 3, traceid=3] ../../source3/winbindd/idmap.c:402(idmap_init_domain) Could not probe idmap module rids [2026/03/03 10:41:25.878035, 3, traceid=3] ../../source3/winbindd/idmap.c:270(idmap_found_domain_backend) idmap_found_domain_backend: Could not init idmap domain windom1 In such a case Winbind should hard fail to start up.