Tim Beale 295bf73e9b dsdb: Handle DB corner-case where PSO container doesn't exist ... A 2003 AD DB with functional level set to >= 2008 was non-functional due to the PSO checks. We already check the functional level is >= 2008 before checking for the PSO container. However, users could change their functional level without ensuring their DB conforms to the corresponding base schema. The objectclass DSDB module should prevent the PSO container from ever being deleted. So the only way we should be able to hit this case is through upgrading the functional level (but not the underlying schema objects). If so, log a low-priority message and continue without errors. BUG: https://bugzilla.samba.org/show_bug.cgi?id=14008 RN: Previously, AD operations such as user authentication could fail completely with the message 'Error 32 determining PSOs in system' logged on the samba server. This problem would only affect a domain that was created using a pre-2008 AD base schema and then had its functional level manually raised to 2008 or greater. This issue has now been resolved. Signed-off-by: Tim Beale <timbeale@catalyst.net.nz> Reviewed-by: Andrew Bartlett <abartlet@samba.org>		2019-06-26 04:12:33 +00:00
..
ldb_modules	dsdb: Handle DB corner-case where PSO container doesn't exist	2019-06-26 04:12:33 +00:00
cracknames.c	cracknames: Change search filter to use the smaller index	2019-02-01 03:36:17 +01:00
samdb_privilege.c	s4-auth Remove event context from privilage database handling	2010-12-21 15:10:38 +11:00
samdb.c	samdb: Add remote address to connect	2018-05-10 20:02:23 +02:00
samdb.h	dsdb: sort DSDB_EXTENDED defines by OID	2018-12-17 04:30:39 +01:00