schakko

Hey there, please take a look into https://wordpress.org/support/topic/locked-configuration-screen/ – the reason for your described error could be same.

It may be that the newer Wordfence does not repackage Monolog in its own namespace. We are doing this since NADI version 3.0. To keep our plug-in compatible, there is a stub.
You can remove our Monolog stub by commenting out the line 40 (require_once DIR . '/monolog_logger.php';) in next-active-directory-integration/src/compat-v2/stubs.php.

Hey there, please take a look into https://wordpress.org/support/topic/locked-configuration-screen/ – the reason for your described error is almost the same.

Your cera theme does not repackage Monolog in its own namespace. We are doing this since NADI version 3.0. To keep our plug-in compatible, there is a stub.
You can remove our Monolog stub by commenting out the line 40 (require_once DIR . '/monolog_logger.php';) in next-active-directory-integration/src/compat-v2/stubs.php. For some reason in your environment the loading of the theme dependency occurs to a later point in time.

We did not test any of those plug-ins. But it may be that those are also hooking in a very specific way into WordPress’ login process. Due to NADI’s SSO functionality we can not guarantee to make it work with any other plug-ins. We would have have to take look at each of those plug-ins separately and get it integrated.

We have just tested BackWPUp 4.1.2 with the latest available NADI version and it works on our side without any problems. Two remarks here:

• BackWPUp 4.1.2 is wrongly packaged. There is the file vendor\monolog\src\Monolog\Handler\ElasticsearchHandler.php and vendor\monolog\src\Monolog\Handler\ElasticSearchHandler.php (note the uppercase ‘S’) in the ZIP file. We had to manually delete the upper-case file from the ZIP files. Otherwise we would not be able to extract the archive manually.
• BackWPUp does not repackage Monolog in its own namespace. We are doing this since NADI version 3.0. To keep our plug-in compatible, there is a stub.
  You can remove our Monolog stub by commenting out the line 40 (require_once DIR . '/monolog_logger.php';) in next-active-directory-integration/src/compat-v2/stubs.php. For some reason in your environment the loading of BackWPUp’s dependency occurs to a later point in time.

Deleting users in WordPress is not implemented:

1. It is not performant to check if a missing user during a synchronization is really deleted or just have been moved to another domain in a forest.
2. For different user (groups) in WordPress there might be a different handling, what to do with items of the deleted user – think of posts, WooCommerce orders and so on. There are too many corner-cases, depending upon the concrete WordPress environment.

Please feel free to use the hooks from https://docs.active-directory-wp.com/API/Synchronization.html to implement a matching solution for your environment!

I’am unable to reproduce the issue with the latest 3.1.0 version. A quick question: Do you have added valid credentials to Sync to WordPress and is the username UPN format and not just the sAMAccountName?

The Account suffix does not apply to SSO authentication, due to technical reasons.

You have two options:

1. Append the users’s UPN suffix in your webserver’s Kerberos authentication module
2. Use the filter from https://docs.active-directory-wp.com/API/Authentication.html to manually rewrite the credentials on each login:

add_filter('next_ad_int_auth_configure_credentials', function($credential) {
$credential->setUpnSuffix('your-upn-suffix.domain');
return $credential;
}, 10, 1);

@lavzza You are probably using PHP 7.x which is EOL since the beginning of the year. NADI requires at least PHP 8.0. So you have to upgrade to a newer PHP version.