schakko
Forum Replies Created
-
– As it is just a warning and not an error it is not so dramatic.
– Please check which AD users generates the above warning. My first guess is that you are synchronizing a service account not having the required LDAP “useraccountcontrol” attribute in his LDAP object schema.Your user above belongs to the security groups “Administrators” and “Staff” but you are mapping the AD groups “administrator” (without ‘s'”) and “Users” to the WordPress role “administrator”.
Forum: Plugins
In reply to: [Next Active Directory Integration] AD Sync not workingThe error you described (“The username or/and email address provided already exist, or result associated, to another existent user account on our forum database.”) seems to originate from the “WP w3all phpBB” plug-in. Please get in contact with their support team as we can’t reproduce this error.
Hi there,
with version 2.1.8 we will add the next_ad_int_loaded hook so you can remove the link generation by yourself. We’ve added an example to our doucmentation: http://active-directory-wp.com/docs/API/Lifecycle.html.Forum: Plugins
In reply to: [Next Active Directory Integration] New User Creation ErrorRegarding the warning: We are not able to reproduce this behavior with WordPress 4.9.x or 5.x, so my guess is that some of your other installed plug-ins interfer. Do you have any mail or user profile related plug-ins installed like BuddyPress?
Can you change the PreventEmailChange.php file so that the line 87 looks likeadd_filter('send_email_change_email', '__return_false'); /* ADD */ if (!is_object($user) || !property_exists($user, 'ID')) { global $wp_actions; print_r($wp_actions['user_profile_update_errors']); debug_print_backtrace(); exit; } /* end ADD */ // $samAccountName = get_user_meta($user->ID, NEXT_AD_INT_PREFIX . 'samaccountname', true);When you try to reproduce the error you should get a stacktrace and all other registered actions for the specific part of code.
Regarding the feature itself: Users who have been added manually in WordPress and have not been authenticated yet by NADI are still able to change their email address. We have adjusted the documentation accordingly.
Forum: Plugins
In reply to: [Next Active Directory Integration] Export/Import SettingsThere is no need to uninstall/reinstall the plug-in when doing an update. By uninstalling the plug-in the whole configuration will be deleted. Just use WordPress’ update mechanism or replace the content of your plugins/next-active-directory-integration directory.
We won’t implement an export/import at this point.Forum: Plugins
In reply to: [Next Active Directory Integration] Authorization groups not working@canadabri
Can you provide an anonymized debug.log? Without this we are not able reproduce your issue.Thank you for this request! NADI does not have any native Gravity Forms integration as it is out of scope for this plug-in.
Nevertheless, you can develop your own dynamically populated dropdown GF field (https://docs.gravityforms.com/dynamically-populating-drop-down-fields/) which uses NADI’s *Dependencies::getInstance()->getLdapConnection()->getAdLdap()* to access the underlying adLDAP library to retrieve values from your AD.Forum: Plugins
In reply to: [Next Active Directory Integration] Password syncNADI does only support synchronization of usernames from the Active Directory to WordPress but not the password. Passwort checks are delegated to the Active Directory.
Forum: Plugins
In reply to: [Next Active Directory Integration] Authorization groups not workingI just want to inform you that we have opened a ticket (ADI-664) in our internal bugtracker to investigate this issue.
- This reply was modified 7 years, 6 months ago by schakko.
Forum: Plugins
In reply to: [Next Active Directory Integration] Menu items missing@5tu Thank you for the reply! I just took a look into it and can confirm it is a bug. I have already fixed but not released it yet. It will be fixed in version 2.1.5.
To circumvent this bug for yet, you can execute the following SQL statement by hand:
UPDATE wp_options SET option_value = ‘1’ WHERE option_name = ‘next_ad_int_bo_v_show_menu_sync_to_wordpress’ OR option_name = ‘next_ad_int_bo_v_show_menu_sync_to_ad’ OR option_name = ‘next_ad_int_bo_v_show_menu_test_authentication’;
Forum: Plugins
In reply to: [Next Active Directory Integration] Menu items missingIn case you are using a multisite installation, I assume your multisite administrator has disabled the options.
Please note that the username (e.g. “microscopicearthling”) in WordPress is *not* sufficient for synchronizing users. You need to append your domain’s UPN suffix by using the User > Account Suffix parameter. With the parameter set, on login the UPN suffix is automatically appended (“microscopicearthling” becomes “microscopicearthling@emea.company.local”). With the full UPN NADI lookup the username inside the Active Directory.
Please also note that for security reasons your first WordPress user will never be authenticated against the AD and so won’t be synchronized during the login process.Forum: Plugins
In reply to: [Next Active Directory Integration] No Data in MySQL@hossmann
Sure, you can join the table wp_usermeta on wp_users like
SELECT u.user_login, um.meta_value FROM wp_users u LEFT JOIN wp_user_meta um ON um.user_id = wp_users.ID WHERE um.meta_key = ‘next_ad_int_${YOUR_PHONE_NUMBER_KEY}’Forum: Plugins
In reply to: [Next Active Directory Integration] Password error after adding SSL– You should be able to log in with your user’s WordPress account who has installed WordPress originally. This user can disable NADI.
– You can move the directory wp-content/plugins/next-active-directory-integration to another folder to disable the plug-in by hand.That being said we are not aware of any NADI issues after applying x509 certificates for TLS/SSL encryption.