schakko

FYI: I’ve just checked the sample in our documentation against the latest NADI, WordPress and wp-crontrol version and it is working fine. Are there any other issues logged?

Hm, NADI does not register its own cronjobs, so I assume that you are using a 3rd party plug-in like wp-crontrol (https://active-directory-wp.com/docs/Usage/How_to_add_a_cron_job_via_Wp_Control.html) which has then be configured to execute the cron job.
As you might have conclude from https://www.ads-software.com/support/topic/cron-unschedule-event-error-for-hook/#post-16185568 this seems to be a bug in either WordPress 6.1.1 or wp-crontrol.

@gate4game NADI should not interfere with WP Rocket. ASFAIR WP Rocket provides only caching functionality but does not alter WordPress’ authentication mechanism.
Can you describe what problems you are experiencing?

No response from thread opener. But this issue might be fixed with 2.3.5, see https://github.com/NeosIT/active-directory-integration2/issues/158,

Ah!
Creating new Active Directory users is outside the scope of NADI due to security and compliance reasons. But you can use the hook next_ad_int_sync_wp2ad_after_user_synchronize to implement such a logic by yourself.

When creating a new user or updating an existing one, the mail AD attribute should already update the user_email field. At least this is working in our test environments.

Hi @marco_b,
yes and no:

For Sync to WordPress, only members of the configured security groups are synchronized. If the security group contains other SGs, those SGs will not be synchronzed.

When a single user is then synchronized to WordPress, all of his security groups (direct or nested) are recurisvely loaded and then mapped to group equivalent WordPress roles.

We have added a how-to to add attributes to the Global Catalog: https://active-directory-wp.com/docs/Configuration/Attributes/Adding_LDAP_attributes_to_the_Global_Catalog.html

You mean that you cannot sync WordPress user to the Active Directory? Did you follow https://active-directory-wp.com/docs/Configuration/Sync_to_AD.html? What are NADI’s debug logs saying?

The field departmentNumber is – by default – not avavilable in the Global Catalog. If you have to use the GC because of other reasons, you have also make the attribute to be replicated in the AD.

Hm, the obvious question is: Does the user you are trying to synchronize have the “departmentNumber” attribute filled? Even if we are both pretty sure that it is filled, can you check with ADSIEdit?

Have connected NADI to your AD’s LDAP port (389, 636) or to the Global Catalog (3268, 3269)?

You can try to var_dump-debug the code in classes/Adi/User/Manager.php (https://github.com/NeosIT/active-directory-integration2/blob/c35e1389669eca9e77df373383472242e63e19b9/classes/Adi/User/Manager.php) line 458 with

// that should contain "departmentnumber" => [...]:
var_dump($ldapAttributes);
// that should contain also "departmentnumber" => [type=>'list']
var_dump($attributeWhitelist);
// that should also contain "departmentnumber" => [...]
var_dump($filteredAttributes);

• This reply was modified 2 years, 6 months ago by schakko.

@marco_b
Hey Marco, can you rename the attribute mapping from “departmentNumber” to “departmentnumber” (lower-case “n”) and check if it works?

Can you elaborate on which WordPress field you are referring to? The “User Disabled” field seems to be coming from another plug-in.

Can you check for any JavaScript errors by using your browser’s Web Developer console (usually, by pressing F12)?