schakko
Forum Replies Created
-
Fixed with latest NADI version 3.2.2
Issue is fixed with NADI 3.2.2
It looks like you are using a PHP version prior to 8.1. Please upgrade to at least 8.1 (or directly to a non-EOL version).
Forum: Plugins
In reply to: [Next Active Directory Integration] Issues SyncingSorry for the late response!
Please enable debug logging (https://docs.active-directory-wp.com/Configuration/Logger.html) and see what’s written in there. It might be the case that you have to set a more specific DN (e.g. cn=Users,dc=batmat,dc=org).
Forum: Plugins
In reply to: [Next Active Directory Integration] Ad user with Custom Login not workingThat is part of our premium extensions. We do not provide any support here.
- This reply was modified 7 months, 3 weeks ago by schakko.
Forum: Plugins
In reply to: [Next Active Directory Integration] Disable new user notification mailNADI does not send any e-mails on its own. It looks like one of your other plug-ins gets triggered when a new user is created.
Active Directory does not provide any realtime notifications for this. You may observe the Windows Event Log for Security-related events – but this is out of scope of NADI.
This has been answered in https://ww.wp.xz.cn/support/topic/issue-connecting-wordpress-to-ad-via-next-adi-plugin/#post-18662041.
This has been answered in https://ww.wp.xz.cn/support/topic/issue-connecting-wordpress-to-ad-via-next-adi-plugin/#post-18662041.
The default OU “Users” is treated special by your Active Directory. Using the root DC is therefore the right way.
It is by default not possible to synchronize users only in specific OU. You have to use security groups for this. Put every user in this OU (and maybe sub-OUs) in a dedicated security group. After you have done that, you have to enable
Import members of security groupsinSync to WordPresstab (https://docs.active-directory-wp.com/Configuration/Sync_to_WordPress.html).Another option would be to use the
sync_ad2wp_filter_user_before_synchronizefilter (https://docs.active-directory-wp.com/API/Synchronization.html) to throw an error if the user would *not* be in the designated OU. When an error is returned, the user will not be synchronized. But that implementation is up to you.Then it’s because your AD cannot be contacted. There can be a number of reasons (see https://docs.active-directory-wp.com/Configuration/Environment.html), e.g.
- IP not reachable from webserver
- LDAP port blocked from webserver’s IP
- Wrong/None encryption selected
Either that or your base DN is misconfigured. You can enable the debug log to see what’s going on behind the scenes (https://docs.active-directory-wp.com/Configuration/Logger.html).
On the environment tab, scroll down to “Verify Credentials” and enter some valid credentials (see https://docs.active-directory-wp.com/Configuration/Environment.html). The message then will disappear.
Forum: Plugins
In reply to: [Next Active Directory Integration] Sync Issues with NADI@dantell71 We have provided a PR for the original issue: https://github.com/NeosIT/active-directory-integration2/pull/212. Can you check it out?