schakko

No response, so I will close this issue.

Specific error handling has been added with version 3.1.8 (https://github.com/NeosIT/active-directory-integration2/issues/203).

@sosere Version 3.1.8 has been released (https://github.com/NeosIT/active-directory-integration2/releases/tag/3.1.8) a few seconds ago ??

Please enable debug logging (https://docs.active-directory-wp.com/Configuration/Logger.html) and look through the created log file. Also try to deactivate any other plug-ins – maybe there is another plug-in intefering.

You can purchase a support plan at https://active-directory-wp.com. Otherwise please take a look at the logged exception. The URL must look like “ldap://your.domain.tld:636”. Please also see https://www.ads-software.com/support/topic/error-since-yesterday-ldap-url-created-in-adldap-class-is-wrong/.

Hi @jcrea,

we have just released a new version v3.8.1-rc1 at https://github.com/NeosIT/active-directory-integration2/releases/tag/v3.1.8-rc1. Can you check if that release fixes the issue?

Hi @slewis1000,

can you please check in NADI’s “Environment” tab the “Domain controllers” and “Port” setting? There is probably a typo (whitespace, special character?) which leads to the error above. We have just released a new pre-release at https://github.com/NeosIT/active-directory-integration2/releases/tag/v3.1.8-rc1 which creates a better error description.

You are welcome, thank you for the feedback! ??

Can you check your Environment tab (https://docs.active-directory-wp.com/Configuration/Environment.html) in NADI? The input field Domain controllers should be your $HOST and not ldaps://$HOST. After you have removed the ldaps://, you have to select the proper Use encryption option.

Hey there, please take a look into?https://www.ads-software.com/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.

NADI should log at least *something*. Could it be that some of your other plug-ins or your theme have been auto-updated? Maybe a plug-in which also extends your authentication?

Hey there, please take a look into https://www.ads-software.com/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 have a very detailled documentation at https://docs.active-directory-wp.com/Getting_Started.html. If you need some onboarding, you can also purchase a support plan + onboarding at https://active-directory-wp.com/shop-overview/.

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.

NADI requires PHP 8.1. The error you are describing means that your PHP version does not support Union Types. I assume that your IIS site has not been assigned with PHP 8.2.x but with an PHP version < 8.x.