schakko

Please take a look at https://github.com/NeosIT/active-directory-integration2/issues/8.

Thanks for the question. With ADI 2 this very behavior is already implemented ??

Authentications done with ADI 2 are preventing any e-mail to be sent. Other users not being authenticated by ADI still receive their registration e-mails.

Most of the settings are automatically migrated. There are some minor cases in which this can not be done, but most of it.

Regarding the release date: we are really sorry about the delay. The plug-in itself is ready to go, but there are organizational tasks which take much longer as expected. Please feel free to give the latest version from https://github.com/NeosIT/active-directory-integration2 a try. Even it is marked as Beta, all functionality works as expected.

closed

We have finished the implementation for support of multiple Active Directory domains on last friday. This feature is only available for Active Directory Integration 2 and will be marked as “experimental”. There are some restrictions when using multiple Active Directories which can not be technically solved b/c of WordPress’ internal structures.

Hey bobchou9,
the development has been done so far. We are currently working on documentation, website and so on which – unfortunately – takes longer as expected. We hope to get the release scheduled in the next weeks. Until then you can give the current beta version a try: https://github.com/NeosIT/active-directory-integration2.

I just want to mention that Azure AD DS should work but at the moment we do not officially support this cloud service.

SSO will be natively implemented in ADI 2 probably later this year. We will provide documentation how to set up WordPress+ADI 2+SSO for different environments.

No, this behavior is not implemented. For ADI 2 we (NeosIT GmbH) can send you an offer to implement such a feature.

I am sorry. The description of the previous version seems to be wrong. For ADI 1.x “TLS” seems to mean “STARTTLS” so it is running on port 389.
LDAPS is still running on 689.

Leaving the port on 389 should be enough.

There could be a problem with your network configuration. The timeout indicates that the AD endpoint can not be contacted. Please note that AD with TLS (not STARTTLS!) is running on port 689 and *not* 389.

We found this issue during ADI 2 development, too and already fixed it. Thank you for the report!

We fixed this issue in ADI 2 by storing the UPN in the wp_user_meta.

In addition to that: With ADI 2 you can exclude specific usernames from AD authentication, even if “Fallback to local password” is disabled.

Hey guys,
a lot is going on in this thread ??

1. With ADI 2 the current behavior is still used. Every AD user is synchronized to WordPress. After the initial synchronization his account gets disabled in WordPress – if disabled in Active Directory. I filled an issue in our backlog but will not promise that we eventually change this behavior.

2. As mrasker already said, we will never delete anything. Deletion is evil.

3. @cityfox this seems to be an issue of BuddyPress. “blocked” is not an official WordPress role. I filled an issue in our backlog. The much cleaner solution would be that we – as the ADI team – provide a hook which is called after disabling a WordPress user. You can listen to this hook and update the WordPress role.

4. @mrasker thank you for the Kerberos hint in https://www.ads-software.com/support/topic/disabled-users-not-showing-up-in-disabled-column?replies=9#post-8293125. I added this to our backlog.