AD authentication fails after upgrade to 3.0.1.0
Posted: 06 May 2016 15:34
All, I was wondering if anyone else was having this problem.
AD integration & authentication was working great in 3.0.0.8 & 3.0.0.9.
After upgrading to 3.0.1.0, no user from AD can authenticate to the MailWatch login page. I've checked all settings, they are still set per all previous AD integration articles; conf.php, functions.php, php-ldap installed, openldap-clients installed, ldpa proxy service account still valid in AD and can login.
I went so far as to edit the /usr/local/bin/mailwatch/tools/Cron_jobs/mailwatch_ldap_sync.sh file with our settings and
re-ran it. That wiped out all the work I had done from consolidating multiple user accounts in the MySQL database.
But, it did re-import all our AD accounts. But still no joy on logins.
The only account that can successfully login, is the built-in Administrator account for EFA.
Any suggestions?
AD integration & authentication was working great in 3.0.0.8 & 3.0.0.9.
After upgrading to 3.0.1.0, no user from AD can authenticate to the MailWatch login page. I've checked all settings, they are still set per all previous AD integration articles; conf.php, functions.php, php-ldap installed, openldap-clients installed, ldpa proxy service account still valid in AD and can login.
I went so far as to edit the /usr/local/bin/mailwatch/tools/Cron_jobs/mailwatch_ldap_sync.sh file with our settings and
re-ran it. That wiped out all the work I had done from consolidating multiple user accounts in the MySQL database.
But, it did re-import all our AD accounts. But still no joy on logins.
The only account that can successfully login, is the built-in Administrator account for EFA.
Any suggestions?