Hi there,

we are using this plugin for years, everything worked fine up to yesterday. Unfortuntately after the last plugin update we got a fatal error. Nobody could log in to the site but the local admin. In the logs we found “PHP Fatal error: Uncaught TypeError: ldap_set_option(): Argument #1 ($ldap) must be of type ?LDAP\Connection, bool given in […]/wp-content/plugins/next-active-directory-integration/src/shared/AdLdap/AdLdap.php:554”. After a little debugging we found out that the URL is composed wrong. It results in “ldap://ldaps://” instead of only “ldaps://”. We are running PHP 8.2 and WordPress 6.6.2. How can we fix this?

When NADI is activated and you try to use DUO Universal Logon (MFA), after receiving the push notification you are redirected back to the login page. If NADI is deactivated, the DUO login works.

Tried Disabling all other plugins as well and only works if NADI is disabled.

Website is not public.

Thanks.

NADI seems to have just stopped working this morning on one of my sites – it’s been working for years prior to that.

When attempting to logon to a site with my LDAP credentials, I receive the error message (on the WP logon page) ‘ERROR: The username or password you entered is incorrect.’

I know the credentials are correct, and in fact if I try a test authentication in the NADI control panel, I can see that the user is logged in – looking at the log output everything looks ok.

If I then attempt to logon at /wp-admin I receive the error again, and even though logging is enabled for the site, I do not see any output in the nadi-debug.log file. This used to work as well. The file is being written to correctly because when I make configuration changes to NADI, I can see information being written to the log. If I use a non-LDAP account I can see logging happening (ending with ‘overridePasswordCheck [line 98] Local WordPress user. Using local (WordPress) password check.’

which seems normal (the local account is logged in ok). If I then try with an LDAP account, no output is written to the log file.

Dear Developer,

just wanted to take a look at your plugin, but was not able to make it work.
As soon as I enable the plugin, wordpress instance crash and send critical error mail and suggests recovery mode. Remove plugin manually will fix it.

Windows Server 2022 – IIS – PHP 8.3.8 – WordPress 6.5.5

Error occured type E_ERROR found in line 231 of file C:\inetpub\wwwroot\intranet\wp-content\plugins\next-active-directory-integration\vendor-repackaged\monolog\monolog\src\Monolog\Logger.php. Errormessage: Uncaught TypeError: Dreitier\Nadi\Vendor\Monolog\Logger::pushHandler(): Argument #1 ($handler) must be of type Dreitier\Nadi\Vendor\Monolog\Handler\HandlerInterface, Monolog\Handler\StreamHandler given, called in C:\inetpub\wwwroot\intranet\wp-content\themes\cera\libs\merlin\includes\class-merlin-logger.php on line 87 and defined in C:\inetpub\wwwroot\intranet\wp-content\plugins\next-active-directory-integration\vendor-repackaged\monolog\monolog\src\Monolog\Logger.php:231

As your plugin sounds quite useful, I would be very happy when you take a look into this issue ??

I want to connect WordPress to the AD using the Next Active Directory Integration plugin so that users can log in to WordPress with their AD credentials, but I don’t understand how the plugin works or where to put the AD connection information such as the password and the username.

I’ve tried a number of WP plugins that allow you to add a login widget to a theme so that users can login directly from the WP site homepage. Those have included:
– Theme My Login
– Login With Ajax
– Login Widget With Shortcode
None of these work properly with the NADI plugin functionality. For an unknown user (to WP), they fail to complete the login process. If you login through the regular WP login page to register the user with the WP site, the login forms work on subsequent logins until there’s some change in the account, like a password change, and then they fail to work again. Are these simply not compatible with the NADI plugin?

When I have WP debugging enabled, I’m seeing this error consistently.

PHP Parse error: syntax error, unexpected ‘|’, expecting variable (T_VARIABLE) in C:\inetpub\wwwroot\wp\wp-content\plugins\next-active-directory-integration\vendor-repackaged\psr\log\src\LoggerInterface.php on line 30

This is on WP 6.5.5 with NADI 3.15 installed on PHP 8.2.0.

I’ve been using the plug-in on a couple WP sites for some time without any problems. Recently, users have been reporting that they couldn’t log into the sites after they changed their password in AD. When I logged into the site and opened the plugin configuration page, none of the settings are accessible. I can see the text and tabs but everything is grayed out.

I know the settings are still in place because when I run a test authentication, it still works for my account (although I get this error – “Query ‘UserQuery={principal=’username@ADname’,isGuid=”}’ did not return any values. Does the sAMAccountName or userPrincipalName exist? Is the provided base DN valid? Is the Kerberos realm mapped”) and users can continue to log in with their previous password. Any ideas on what might be causing this?

Thanks!

System specs:
Windows Server 2016
IIS – 10.0.14393.0
WP – 6.5.5
PHP – 8.3.8
Plugin – 3.1.4

Hellooo,

Is there a way to make sure that users in WordPress are deleted after synchronisation if they are deleted in AD ?

Hello,

I observed that AD users get logged out at irregular intervals before the session expires (wp_logged_in). I turned off other plugins but problem remains.

Does anyone know what might be causing this?
Is there some setting I maybe have overseen?

Problem detected in Sync to WordPress function
Dreitier\Nadi\User\Meta\Persistence\Repository::disableUser(): Argument #1 ($userData) must be of type WP_User, bool given, called in /var/www/mywebsite/wp-content/plugins/next-active-directory-integration/src/plug-in/User/Manager.php on line 764

I can logon with AD, but not with SSO
Account suffix on page "User" is set to @domain.com
I logged on with mySAM user name and try to open site home page.
Site opens without user bar. 
Log records:
2023-09-18T09:51:59.684270+00:00 [DEBUG] Dreitier\Nadi\Authentication\SingleSignOn\Service::findUsername [line 250] SSO provided username for environment variable "REMOTE_USER" is "mySAM'
2023-09-18T09:51:59.684550+00:00 [DEBUG] Dreitier\Nadi\Authentication\LoginService::getWordPressUser [line 479] Local WordPress user 'mySAM' could not be found
2023-09-18T09:51:59.684759+00:00 [DEBUG] Dreitier\Nadi\Authentication\SingleSignOn\Profile\Locator::locateBySuffix [line 95] Looking up SSO profile by UPN suffix fallback for credential 'Credentials={login='mySAM',sAMAccountName='mySAM',userPrincipalName='mySAM',netbios='',objectGuid='',wordPressUserId='',kerberosRealm=''}'
2023-09-18T09:52:00.025217+00:00 [DEBUG] Dreitier\Nadi\Authentication\SingleSignOn\Profile\Locator::locate [line 66] Profile match:
2023-09-18T09:52:00.025314+00:00 [ERROR] Dreitier\Nadi\Authentication\SingleSignOn\Service::authenticate [line 160] User could not be authenticated using SSO. Unable to locate a matching profile for 'mySAM'

But if I logon using wp-login.php, I can access wordpress and see my login on "Users" page with [NADI User] flag set.
I can login with only sAMAccount or sAMAccount + domain. Both accounts are working.

When I use "Test authentication" page, I successfully logon, Log output is:

INFO System Information:
INFO - PHP: "8.1.12"
INFO - WordPress: "6.3.1"
INFO - Active Directory Integration: "3.0"
INFO - Operating System: "Linux wp.domain.com 5.4.0-110-generic Ubuntu SMP Mon Apr 10 21:37:12 UTC 2023 x86_64"
INFO - Web Server: "fpm-fcgi"
INFO - adLDAP: "3.3.3 EXTENDED (20221201)"
INFO *** Establishing Active Directory connection ***
INFO A user tries to log in.
DEBUG Credentials={login='mySAM',sAMAccountName='mySAM',userPrincipalName='mySAM',netbios='',objectGuid='',wordPressUserId='',kerberosRealm=''}' with authenticatable suffixes: '@DOMAIN.COM'.
INFO LDAP connection is not encrypted
DEBUG account_suffix =
DEBUG base_dn = DC=domain,DC=com
DEBUG domain_controllers = domain.com
DEBUG ad_port = 389
DEBUG use_tls =
DEBUG use_ssl =
DEBUG network_timeout = 5
DEBUG allow_self_signed =
DEBUG ad_username =
DEBUG ad_password =
WARNING Username for the sync user does not contain a correct suffix. If the connection to the ad fails, this could be the cause. Please make sure you have added all UPN suffixes to the configuration tab User -> Account suffix.
DEBUG Trying to authenticate user with username 'mySAM' and account suffix '@DOMAIN.COM'
DEBUG Authentication successful for username 'mySAM' and account suffix '@DOMAIN.COM'.
WARNING Query 'UserQuery={principal='[email protected]',isGuid=''}' did not return any values. Does the sAMAccountName or userPrincipalName exist? Is the provided base DN valid? Is the Kerberos realm mapped
DEBUG UserInfo for user 'UserQuery={principal='mySAM',isGuid=''}': cn={mySurname, myName}, sn={mySurname}, description={myName mySurname}, givenname={myName}, displayname={myName mySurname}, objectguid={59a23c-1111-4234-2222-f346710a44a}, useraccountcontrol={512}, objectsid={H3N?jP4U?D?u}}, samaccountname={mySAM}, userprincipalname={[email protected]}, mail={[email protected]}
[STATUS] User logged on.

What am I doing wrong?

Hello.

I get fatal error. Can you help me?

Fatal error: Uncaught Error: syntax error, unexpected '|', expecting variable (T_VARIABLE)
in /var/www/html/wp-content/plugins/next-active-directory-integration/vendor-repackaged/psr/log/src/LoggerInterface.php on line 30

Call stack:

{closure}()
spl_autoload_call()
wp-content/plugins/next-active-directory-integration/vendor-repackaged/monolog/monolog/src/Monolog/Logger.php:40
require_once()
wp-content/plugins/next-active-directory-integration/vendor-repackaged/autoload.php:10
{closure}()
spl_autoload_call()
wp-content/plugins/next-active-directory-integration/src/plug-in/Log/Logger.php:11
include_once()
wp-content/plugins/next-active-directory-integration/autoload.php:49
{closure}()
spl_autoload_call()
wp-content/plugins/next-active-directory-integration/src/plug-in/Log/NadiLog.php:60
Dreitier\N\L\NadiLog::createLogger()
wp-content/plugins/next-active-directory-integration/src/plug-in/Log/NadiLog.php:42
Dreitier\N\L\NadiLog::getInstance()
wp-content/plugins/next-active-directory-integration/src/plug-in/Requirements.php:30
Dreitier\Nadi\Requirements::__construct()
wp-content/plugins/next-active-directory-integration/index.php:33
include_once()
wp-admin/includes/plugin.php:2318
plugin_sandbox_scrape()
wp-admin/plugins.php:192
Query Monitor

Parse error: syntax error, unexpected '|', expecting variable (T_VARIABLE) in /var/www/html/wp-content/plugins/next-active-directory-integration/vendor-repackaged/psr/log/src/LoggerInterface.php on line 30

Fatal error: Exception thrown without a stack frame in Unknown on line 0

I am trying to update the NADI plugin form 2.1.11 to 3.0.5. on 2.1.11, the ‘Sync to WordPress’ works, but when I upgrade to 3.0.5 I get:

Fatal error: Uncaught Error: Call to a member function getFormatted() on null in /var/www/reslifedashboard/wp-content/plugins/next-active-directory-integration/src/shared/Ldap/Connection.php:737 Stack trace: #0 /var/www/reslifedashboard/wp-content/plugins/next-active-directory-integration/src/shared/Ldap/Connection.php(706): Dreitier\Ldap\Connection->filterDomainMembers() #1 /var/www/reslifedashboard/wp-content/plugins/next-active-directory-integration/src/plug-in/Synchronization/WordPressSynchronizationService.php(225): Dreitier\Ldap\Connection->findAllMembersOfGroups() #2 /var/www/reslifedashboard/wp-content/plugins/next-active-directory-integration/src/plug-in/Synchronization/WordPressSynchronizationService.php(124): Dreitier\Nadi\Synchronization\WordPressSynchronizationService->findSynchronizableUsers() #3 /var/www/reslifedashboard/wp-content/plugins/next-active-directory-integration/src/plug-in/Synchronization/Ui/SyncToWordPressPage.php(119): Dreitier\Nadi\Synchronization\WordPressSynchronizationService->synchronize() #4 /var/www/reslifedashboard/wp-content/plugins/next-active-directory-integration/src/plug-in/Synchronization/Ui/SyncToWordPressPage.php(74): Dreitier\Nadi\Synchronization\Ui\SyncToWordPressPage->processData() #5 /var/www/reslifedashboard/wp-includes/class-wp-hook.php(308): Dreitier\Nadi\Synchronization\Ui\SyncToWordPressPage->renderAdmin() #6 /var/www/reslifedashboard/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters() #7 /var/www/reslifedashboard/wp-includes/plugin.php(517): WP_Hook->do_action() #8 /var/www/reslifedashboard/wp-admin/admin.php(259): do_action() #9 {main} thrown in?/var/www/reslifedashboard/wp-content/plugins/next-active-directory-integration/src/shared/Ldap/Connection.php?on line?737

below is ‘Site Health’ ‘Info’

wp-core

version: 6.2
site_language: en_US
user_language: en_US
timezone: America/New_York
permalink: /%postname%/
https_status: true
multisite: false
user_registration: 0
blog_public: 0
default_comment_status: closed
environment_type: production
user_count: 5056
dotorg_communication: true

wp-paths-sizes

wordpress_path: /var/www/reslifedashboard
wordpress_size: 390.46 MB (409427462 bytes)
uploads_path: /var/www/reslifedashboard/wp-content/uploads
uploads_size: 4.18 GB (4490937624 bytes)
themes_path: /var/www/reslifedashboard/wp-content/themes
themes_size: 40.20 MB (42149692 bytes)
plugins_path: /var/www/reslifedashboard/wp-content/plugins
plugins_size: 170.55 MB (178835445 bytes)
database_size: 349.50 MB (366481584 bytes)
total_size: 5.11 GB (5487831807 bytes)

wp-active-theme

name: Divi Child Theme (Divi-Child)
version: 1.0.1
author: Maryann Reissig
author_website: https://reslifedashboard.sjfc.edu
parent_theme: Divi (Divi)
theme_features: core-block-patterns, widgets-block-editor, custom-background, automatic-feed-links, post-thumbnails, menus, title-tag, post-formats, woocommerce, wc-product-gallery-zoom, wc-product-gallery-lightbox, wc-product-gallery-slider, customize-selective-refresh-widgets, editor-style, widgets
theme_path: /var/www/reslifedashboard/wp-content/themes/Divi-Child
auto_update: Disabled

wp-parent-theme

name: Divi (Divi)
version: 3.25.4 (latest version: 4.20.4)
author: Elegant Themes
author_website: https://www.elegantthemes.com
theme_path: /var/www/reslifedashboard/wp-content/themes/Divi
auto_update: Disabled

wp-themes-inactive (6)

Twenty Nineteen: version: 1.9, author: the WordPress team (latest version: 2.5), Auto-updates disabled
Twenty Sixteen: version: 2.3, author: the WordPress team (latest version: 2.9), Auto-updates disabled
Twenty Twenty: version: 1.6, author: the WordPress team (latest version: 2.2), Auto-updates disabled
Twenty Twenty-One: version: 1.5, author: the WordPress team (latest version: 1.8), Auto-updates disabled
Twenty Twenty-Three: version: 1.1, author: the WordPress team, Auto-updates disabled
Twenty Twenty-Two: version: 1.1, author: the WordPress team (latest version: 1.4), Auto-updates disabled

wp-mu-plugins (1)

ET Support Center :: Must-Use Plugins Autoloader: author: Elegant Themes, version: (undefined)

wp-plugins-active (33)

Admin Bar Disabler: version: 1.4.2, author: Scott Kingsley Clark, Auto-updates disabled
Akismet Anti-Spam: Spam Protection: version: 5.1, author: Automattic - Anti Spam Team, Auto-updates disabled
BackupBuddy: version: 8.7.5, author: iThemes, Auto-updates disabled
Better Font Awesome: version: 2.0.4, author: Mickey Kay, Auto-updates disabled
Check & Log Email: version: 1.0.7, author: WPChill, Auto-updates disabled
Classic Editor: version: 1.6.3, author: WordPress Contributors, Auto-updates disabled
Defender Pro: version: 2.8.3, author: WPMU DEV (latest version: 3.10.1), Auto-updates disabled
Enable Media Replace: version: 4.1.1, author: ShortPixel, Auto-updates disabled
gAppointments: version: 1.9.5.2, author: WpCrunch, Auto-updates disabled
Gravity Flow: version: 2.9.2, author: Gravity Flow, Auto-updates disabled
Gravity Forms: version: 2.7.4, author: Gravity Forms, Auto-updates enabled
Gravity Forms Data Persistence Add-On Reloaded: version: 3.3.1, author: Robert Iseley, Auto-updates disabled
Gravity Forms Zapier Add-On: version: 4.2, author: Gravity Forms, Auto-updates disabled
GravityMath: version: 2.3.2, author: GravityKit, Auto-updates disabled
GravityView: version: 2.17.5, author: GravityKit, Auto-updates disabled
GravityView - Advanced Filter Extension: version: 2.2, author: GravityKit, Auto-updates disabled
GravityView - DataTables Extension: version: 2.6, author: The GravityView Team, Auto-updates disabled
Groups Assigner: version: 1.0.0, author: M Reissig, Auto-updates disabled
ICS Calendar: version: 10.11.0, author: Room 34 Creative Services, LLC, Auto-updates disabled
LoginPress - Customizing the WordPress Login Screen.: version: 1.7.1, author: WPBrigade, Auto-updates disabled
LoginWP (Formerly Peter's Login Redirect): version: 3.0.7.0, author: LoginWP Team, Auto-updates disabled
Members: version: 3.2.4, author: MemberPress, Auto-updates disabled
Memphis Documents Library: version: 3.10.10, author: Ian Howatson, Auto-updates disabled
My Private Site: version: 3.0.13, author: David Gewirtz, Auto-updates disabled
Nav Menu Roles: version: 2.1.2, author: Kathy Darling, Auto-updates disabled
Next Active Directory Integration: version: 3.0.5, author: active-directory-wp.com, Auto-updates disabled
Really Simple SSL: version: 6.2.4, author: Really Simple Plugins, Auto-updates disabled
Snapshot Pro: version: 3.3.2, author: WPMU DEV, Auto-updates disabled
Surbma | Divi Remove Project CPT: version: 2.0, author: Surbma, Auto-updates disabled
User Switching: version: 1.7.0, author: John Blackbourn & contributors, Auto-updates disabled
WPMU DEV Dashboard: version: 4.11.12, author: WPMU DEV (latest version: 4.11.18), Auto-updates disabled
WP Rollback: version: 1.7.3, author: GiveWP.com, Auto-updates disabled
Yoast Duplicate Post: version: 4.5, author: Enrico Battocchi & Team Yoast, Auto-updates disabled

wp-plugins-inactive (1)

maintenance_mode: version: 1.0, author: Steve Vaughn, Auto-updates disabled

wp-media

image_editor: WP_Image_Editor_GD
imagick_module_version: Not available
imagemagick_version: Not available
imagick_version: Not available
file_uploads: File uploads is turned off
post_max_size: 128M
upload_max_filesize: 128M
max_effective_size: 128 MB
max_file_uploads: 20
gd_version: 2.3.3
gd_formats: GIF, JPEG, PNG, WebP, BMP, XPM
ghostscript_version: not available

wp-server

server_architecture: Linux 4.18.0-425.19.2.el8_7.x86_64 x86_64
httpd_software: Apache/2.4.37 (Red Hat Enterprise Linux) OpenSSL/1.1.1k
php_version: 8.0.28 64bit
php_sapi: fpm-fcgi
max_input_variables: 1000
time_limit: 250
memory_limit: 512M
max_input_time: 60
upload_max_filesize: 128M
php_post_max_size: 128M
curl_version: 7.61.1 OpenSSL/1.1.1k
suhosin: false
imagick_availability: false
pretty_permalinks: true
htaccess_extra_rules: true

wp-database

extension: mysqli
server_version: 10.3.35-MariaDB
client_version: mysqlnd 8.0.28
max_allowed_packet: 16777216
max_connections: 151

wp-constants

WP_HOME: https://reslifedashboard-pprd.sjf.edu
WP_SITEURL: https://reslifedashboard-pprd.sjf.edu
WP_CONTENT_DIR: /var/www/reslifedashboard/wp-content
WP_PLUGIN_DIR: /var/www/reslifedashboard/wp-content/plugins
WP_MEMORY_LIMIT: 40M
WP_MAX_MEMORY_LIMIT: 512M
WP_DEBUG: true
WP_DEBUG_DISPLAY: true
WP_DEBUG_LOG: /var/www/reslifedashboard/wp-content/debug.log
SCRIPT_DEBUG: false
WP_CACHE: false
CONCATENATE_SCRIPTS: undefined
COMPRESS_SCRIPTS: undefined
COMPRESS_CSS: undefined
WP_ENVIRONMENT_TYPE: Undefined
DB_CHARSET: utf8
DB_COLLATE: undefined

wp-filesystem

wordpress: writable
wp-content: writable
uploads: writable
plugins: writable
themes: writable
mu-plugins: writable

I am trying to update the NADI plugin form 2.1.11 2.2.0. on 2.1.11, the Sync to WordPress works, but when I upgrade to 2.2.0 I get:

Fatal error: Uncaught TypeError: Argument 1 passed to NextADInt_ActiveDirectory_Context::isMember() must be an instance of NextADInt_ActiveDirectory_Sid, null given, called in /var/www/reslifedashboard/wp-content/plugins/next-active-directory-integration/classes/Adi/Synchronization/Abstract.php on line 171 and defined in /var/www/reslifedashboard/wp-content/plugins/next-active-directory-integration/classes/ActiveDirectory/Context.php:65 Stack trace: #0 /var/www/reslifedashboard/wp-content/plugins/next-active-directory-integration/classes/Adi/Synchronization/Abstract.php(171): NextADInt_ActiveDirectory_Context->isMember(NULL) #1 /var/www/reslifedashboard/wp-content/plugins/next-active-directory-integration/classes/Adi/Synchronization/Abstract.php(117): NextADInt_Adi_Synchronization_Abstract->findActiveDirectoryUsers() #2 /var/www/reslifedashboard/wp-content/plugins/next-active-directory-integration/classes/Adi/Synchronization/WordPress.php(217): NextADInt_Adi_Synchronization_Abstract->findActiveDirectoryUsernames() #3 /var in?/var/www/reslifedashboard/wp-content/plugins/next-active-directory-integration/classes/ActiveDirectory/Context.php?on line?65

This dispite the fact that the credentials haven’t change and when I verify them on the ‘Environment’ tab, it says ‘Verifiation Succesful’.

When I roll back to 2.1.11, the sync works again

Our recent upgrade may have caused an issue where users are no longer able to consistently log in to our WordPress website.
Here are our settings
Next Active Directory Version 3.0.5
WordPress: 6.1

PHP Version: 8.02
Our Plugin Settings: Link

Error from PHP Log
thrown in wp-content\plugins\next-active-directory-integration\src\shared\Ldap\Attribute\Converter.php on line 92

inetpub\wwwroot\hcsdweb\insider\wp-includes\class-wp-hook.php(308): Dreitier\Nadi\User\LoginSucceededService->updateOrCreateUser()

I changed my AD password and WP allowed me to log in with OLD and NEW pass till I used AD-WP-synch .

can this be done instantly ? change AD-pass – old becomes invalid for WP

thank you

• This topic was modified 1 year, 7 months ago by mihailantibor.

Hi,
unfortunately I get another error when I try to assign the profile. Here is the extract from the Errog log:

Uncaught Error: Class "WP_MS_Sites_List_Table" not found in /var/www/html/wp-content/plugins/next-active-directory-integration/src/shared/WordPress/Multisite/Ui/Table/ProfileAssignment.php:14
Stack trace:
#0 /var/www/html/wp-content/plugins/next-active-directory-integration/autoload.php(49): include_once()
#1 /var/www/html/wp-content/plugins/next-active-directory-integration/src/shared/WordPress/Multisite/Ui/BlogProfileRelationshipController.php(167): {closure}()
#2 /var/www/html/wp-content/plugins/next-active-directory-integration/src/shared/WordPress/Multisite/Ui/BlogProfileRelationshipPage.php(104): Dreitier\\WordPress\\Multisite\\Ui\\BlogProfileRelationshipController->buildSiteTable()
#3 /var/www/html/wp-includes/class-wp-hook.php(303): Dreitier\\WordPress\\Multisite\\Ui\\BlogProfileRelationshipPage->renderNetwork()
#4 /var/www/html/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters()
#5 /var/www/html/wp-includes/plugin.php(470): WP_Hook->do_action()
#6 /var/www/html/wp-admin/admin.php(259): do_action()
#7 /var/www/html/wp-admin/network/admin.php(13): require_once('...')
#8 {main}
  thrown in /var/www/html/wp-content/plugins/next-active-directory-integration/src/shared/WordPress/Multisite/Ui/Table/ProfileAssignment.php on line 14
  

Can you take a look at it?

Many thanks and best regards
Schorsch

Hello, I set up the plugin and successfully synchronized the users from the Active Directory to WordPress. Unfortunately, I cannot log in with the Active Directory password. Login works with a local password.

Error from the log:

2023-03-20T09:10:52.068501+00:00 [DEBUG] Dreitier\Nadi\Authentication\LoginService::getWordPressUser [line 484] User ‘1234’ has local WordPress ID ‘2’.
2023-03-20T09:10:52.070186+00:00 [DEBUG] Dreitier\Nadi\Authentication\LoginService::tryAuthenticableSuffixes [line 249] Credentials={login=’1234′,sAMAccountName=’1234′,userPrincipalName=’1234′ ,netbios=”,objectGuid=”,wordPressUserId=”,kerberosRealm=”}’ with authenticatable suffixes: ”.
2023-03-20T09:10:52.070283+00:00 [WARNING] Dreitier\Nadi\Authentication\LoginService::tryAuthenticatableSuffixes [line 267] Login for Credentials={login=’1234′,sAMAccountName=’1234′,userPrincipalName=’ 1234′,netbios=”,objectGuid=”,wordPressUserId=”,kerberosRealm=”} failed: none of the suffixes succeeded

Can you help me find the wrong setting?

Best regards,

Sebastian

I get a critical error when I log into wordpress (Network) via the plugin. Even with the 3.0.2 update, the error persists.

Uncaught Error: Class "Dreitier\\Util\\Logger\\LogFacade" not found in /var/www/html/wp-content/plugins/next-active-directory-integration/src/shared/WordPress/WordPressErrorException.php:50
Stack trace:
#0 /var/www/html/wp-content/plugins/next-active-directory-integration/src/plug-in/User/Manager.php(642): Dreitier\\WordPress\\WordPressErrorException::processWordPressError()
#1 /var/www/html/wp-content/plugins/next-active-directory-integration/src/plug-in/User/Manager.php(577): Dreitier\Nadi\\User\\Manager->handleEmailAddressOfUser()
#2 /var/www/html/wp-content/plugins/next-active-directory-integration/src/plug-in/User/Manager.php(321): Dreitier\Nadi\\User\\Manager->updateEmail()
#3 /var/www/html/wp-content/plugins/next-active-directory-integration/src/plug-in/User/LoginSucceededService.php(220): Dreitier\Nadi\\User\\Manager->update()
#4 /var/www/html/wp-content/plugins/next-active-directory-integration/src/plug-in/User/LoginSucceededService.php(150): Dreitier\Nadi\\User\\LoginSucceededService->updateUser()
#5 /var/www/html/wp-includes/class-wp-hook.php(303): Dreitier\Nadi\\User\\LoginSucceededService->updateOrCreateUser()
#6 /var/www/html/wp-includes/plugin.php(189): WP_Hook->apply_filters()
#7 /var/www/html/wp-content/plugins/next-active-directory-integration/src/plug-in/User/LoginSucceededService.php(85): apply_filters()
#8 /var/www/html/wp-includes/class-wp-hook.php(303): Dreitier\Nadi\\User\\LoginSucceededService->updateOrCreateAfterSuccessfulLogin()
#9 /var/www/html/wp-includes/plugin.php(189): WP_Hook->apply_filters()
#10 /var/www/html/wp-includes/pluggable.php(588): apply_filters()
#11 /var/www/html/wp-includes/user.php(95): wp_authenticate()
#12 /var/www/html/wp-login.php(1142): wp_signon()
#13 {main}
  thrown in /var/www/html/wp-content/plugins/next-active-directory-integration/src/shared/WordPress/WordPressErrorException.php on line 50

Can you understand and fix this?

Hi, we run NADI on three client sites. The servers in question all run PHP 7.4 currently.

Updating to NADI 3.0.2 caused a fatal error and the sites were inaccessible. Rolling back to NADI 2.3.7 fixed the issue.

Here’s what I pulled from the PHP error_log on one of the sites:

[03-Mar-2023 17:20:48 UTC] PHP Parse error:  syntax error, unexpected '|', expecting variable (T_VARIABLE) in /home/mysitename/public_html/wp-content/plugins/next-active-directory-integration/vendor-repackaged/psr/log/src/LoggerInterface.php on line 30

I am running PHP 8.2 and NADI 3.0 kicks a critical error.
Is 8.2 supported?

Our site is unavailable after the update to 3.0.

syntax error, unexpected ‘|’, expecting variable (T_VARIABLE) in E:\apps\c3-circuitcourtintranet\c3-circuitcourtintranet-cms\wp-content\plugins\next-active-directory-integration\vendor-repackaged\psr\log\src\LoggerInterface.php on line 30

With the upcoming version NADI 3.0.0 on March 01, 2022, there might be breaking changes for some of you.

Please read carefully the milestone description at https://github.com/NeosIT/active-directory-integration2/milestone/11.

We’ve just upgraded WP from 6.0.3 to 6.1.1 (PHP 8.1) and we’re now seeing this kind of error message in the debug.log file when the NADI plugin tries to sync AD to WP, with sensitive data obfuscated:

[24-Nov-2022 11:54:42 UTC] Cron reschedule event error for hook: crontrol_cron_job, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:”daily”,”args”:{“code”:” $postData = http_build_query( \r\n array(\r\n ‘next_ad_int-task’ => ‘sync-to-wordpress’,\r\n ‘auth-code’ => ‘xxxxxxxxxxx’\r\n )\r\n );\r\n $data_len = strlen($postData);\r\n $opts = array(\r\n ‘http’ => array( \r\n ‘method’ => ‘POST’,\r\n\t\t ‘header’ => \”Content-Type: application\/x-www-form-urlencoded\\r\\nConnection: close\\r\\nContent-Length: $data_len\\r\\n\”,\r\n ‘content’ => $postData\r\n )\r\n );\r\n $context = stream_context_create($opts);\r\n $result = file_get_contents(‘http:\/\/AAA.BBB.COM\/wp-admin\/admin.php’, false, $context);\r\n”,”name”:”AD Sync to WP”},”interval”:86400}`

In fact, there appears to be two identical “PHP Cron (AD Sync to WP)” jobs listed in the cron list), neither of which we can delete. Any help with the issue would be much appreciated.

I have a compatibility problem with the wp rocket plugin. Does anyone have any experience? Is it possible to use this plugin with wp rocket plugin?

Hi there

Can NADI handle groups in group from AD?

Best regards,
Marco

how to force synch ‘mail’ attribute from AD to WP user[user_email]?

Hi all
Is this plugin can sync the new user to AD from WP?
I tested Sync to AD and Sync to WordPress, it can sync new user to WP from AD,
but can not sync new user to WP from AD.

Hi there

I would like to sync the AD attribute “departmentNumber” the type in AD is “Multi-valued String”. In the configuration I selected the type “list” other AD fields of this type are synced. What could be wrong?

2022-09-22 08:32:41 [DEBUG] NextADInt_Adi_User_Manager::{closure} [line 538] AD attribute ‘departmentNumber” is empty. Local value ‘Attribute next_ad_int_departmentNumber={type=’list’, syncable=”, viewable=’1′, overwriteWithEmpty=’}’ left unchanged.

Best regards
Marco