Support » Plugin: Next Active Directory Integration » Worpress cannot operate anymore after activating NADI

  • Resolved florianbad

    (@florianbad)


    Dear Sir or Madam,

    we use in our company internally a WordPress page for our Intranet. So it is not reachable thorugh the Internet. Right now we upgraded our PHP version to 7.3.1 and also updated WordPress to 5.7. Now we have the problem, that when NADI is activated the Worpress is not usable anymore. We also get the following error message:
    Technical issue

    WordPress version 5.7
    Current theme: First (version 2.0.2)
    Current plugin: Next Active Directory Integration (version 2.2.2) PHP version 7.3.1

    Error Details
    =============
    An error of type E_ERROR was caused in line 165 of the file C:\XAMPP\htdocs\wordpress\wp-content\plugins\next-active-directory-integration\classes\Adi\Authentication\SingleSignOn\Service.php. Error message: Uncaught Error: Call to a member function getProfile() on null in C:\XAMPP\htdocs\wordpress\wp-content\plugins\next-active-directory-integration\classes\Adi\Authentication\SingleSignOn\Service.php:165
    Stack trace:
    #0 C:\XAMPP\htdocs\wordpress\wp-content\plugins\next-active-directory-integration\classes\Adi\Authentication\SingleSignOn\Service.php(125): NextADInt_Adi_Authentication_SingleSignOn_Service->delegateAuth(Object(NextADInt_Adi_Authentication_Credentials), Object(NextADInt_Adi_Authentication_SingleSignOn_Validator))
    #1 C:\XAMPP\htdocs\wordpress\wp-includes\class-wp-hook.php(292): NextADInt_Adi_Authentication_SingleSignOn_Service->authenticate(”)
    #2 C:\XAMPP\htdocs\wordpress\wp-includes\class-wp-hook.php(316): WP_Hook->apply_filters(NULL, Array)
    #3 C:\XAMPP\htdocs\wordpress\wp-includes\plugin.php(484): WP_Hook->do_action(Array)
    #4 C:\XAMPP\htdocs\wordpress\wp-settings.php(560): do_action(‘init’)
    #5 C:\XAMPP\htdocs\wordpress\wp-config.php(84): require_once(‘C:\\XAMPP\\htdocs…’)
    #6 C:\XAMPP\htdocs\word`

Viewing 15 replies - 1 through 15 (of 16 total)
  • Plugin Author schakko

    (@schakko)

    Hi @florianbad ,
    – did NADI worked before the update to 2.2.2?
    – did you have changed anything prior to the PHP and/or WordPress update?

    Please enable NADI’s debug.log as described in https://active-directory-wp.com/docs/Configuration/Logger.html to see what this causes the error. My best shot would be that your Apache does not forward the Kerberos credentials if you have SSO enabled.

    Thread Starter florianbad

    (@florianbad)

    Hi @schakko
    First thanks for your quick reply.

    The NADI addon worked the whole time. The interesting thing was it also worked when our PHP still was a very old version.
    Now we updated the PHP version that we can use NADI again. When we deactivate NADI everything works. And irritating is: when we deactivate NADI, log in to the administration and then activate it again the plug in is activated. We can check the configuration and everything. But when we want to synchronize it fails.

    Until now we also didnt activated any new plugins that there would be a problem with cross errors.

    So there is a log existing. The times mentioned are interessting and because it is a company site there are some details that have information from our internal network. I know that is not the best way but is there an option I can lookout for?

    Plugin Author schakko

    (@schakko)

    – Are you using Kerberos/SSO?
    – Is your WordPress instance a multisite instance?

    In the debug.log there should something like
    – “Looking up SSO profile by NETBIOS name for credential…”
    – or “Looking up SSO profile by Kerberos realm for credential..”
    – or “Looking up SSO profile by UPN suffix fallback for credential..”

    and after that “Profile match: “.
    This is the interesting part.

    Thread Starter florianbad

    (@florianbad)

    @schakko
    Update: So I activated the add in again to get a new log entry and the interessting thing is: he can connect to the AD with the information given. In the log I can see all the user details and what he is sharing. So I can see details from our AD structure (groups and users) that he can only see with access to the AD.
    But also when the log shows a status that the import works the WordPress page shows the following error when we initiate the AD sync by button click: “There has been a critical error on this website. Please check your site admin email inbox for instructions.”

    Plugin Author schakko

    (@schakko)

    @florianbad The error log you had posted in first post has no (atleast should not have) correlation to the “Sync to WordPress” feature. Can you check the PHP error log again?

    Thread Starter florianbad

    (@florianbad)

    @schakko
    I think you are right because the logs shows users he can find but the import was not done to WordPress.

    Now you have to bear a little bit with me: what exact log can I search for? the information from the first post are from an automated created e mail from WordPress with error information.

    Plugin Author schakko

    (@schakko)

    @florianbad It depends upon your webserver enviroment. You can look into Apache’s error_log or a custom log configured for PHP-FPM.

    Thread Starter florianbad

    (@florianbad)

    @schakko

    So I found the PHP log file and there was this entry:

    [03-May-2021 09:54:14 UTC] PHP Warning: A non-numeric value encountered in C:\XAMPP\htdocs\wordpress\wp-content\plugins\next-active-directory-integration.hold\classes\Adi\Synchronization\WordPress.php on line 345
    [03-May-2021 09:54:14 UTC] PHP Fatal error: Uncaught Error: Call to a member function getDomainPartAsSid() on null in C:\XAMPP\htdocs\wordpress\wp-content\plugins\next-active-directory-integration.hold\classes\Adi\Synchronization\WordPress.php:419
    Stack trace:
    #0 C:\XAMPP\htdocs\wordpress\wp-content\plugins\next-active-directory-integration.hold\classes\Adi\Synchronization\WordPress.php(133): NextADInt_Adi_Synchronization_WordPress->synchronizeUser(Object(NextADInt_Adi_Authentication_Credentials), ’40b57468-6afc-4…’)
    #1 C:\XAMPP\htdocs\wordpress\wp-content\plugins\next-active-directory-integration.hold\classes\Adi\Synchronization\Ui\SyncToWordPressPage.php(114): NextADInt_Adi_Synchronization_WordPress->synchronize()
    #2 C:\XAMPP\htdocs\wordpress\wp-content\plugins\next-active-directory-integration.hold\classes\Adi\Synchronization\Ui\SyncToWordPressPage.php(69): NextADInt_Adi_Synchronization_Ui_SyncToWordPressPage->processData(Array)
    #3 C:\XAMPP\htdocs\wordpress\wp-includes\class-wp-hook.php(292): NextADInt_Adi_Synchronization_Ui_SyncToWordPressPage->r in C:\XAMPP\htdocs\wordpress\wp-content\plugins\next-active-directory-integration.hold\classes\Adi\Synchronization\WordPress.php on line 419`

    Plugin Author schakko

    (@schakko)

    Ah okay, this is already tracked at https://github.com/NeosIT/active-directory-integration2/issues/141 and fixed in 2.2.3 which is planned to be released tomorrow 😉

    Thread Starter florianbad

    (@florianbad)

    @schakko
    Ah okay sorry that I didnt follwed up. But thanks for clearing it up. Then I will install the update tomorrow and will have a look at it.

    When it is resolved I will post the result here so we can close the thread.

    Thanks anyway for your quick and prompt support.

    Thread Starter florianbad

    (@florianbad)

    @schakko
    The problem is solved with the update. Thanks again for the detailled and quick help. I had to re-add the plugin again to the plugins folder but maybe this was only an issue of our installation.

    Kind regards.

    Plugin Author schakko

    (@schakko)

    @florianbad That’s good to hear 🙂

    Thread Starter florianbad

    (@florianbad)

    @schakko
    Okay I maybe was a little bit fast. It seems that I used by accident a cached website and that this was working.
    But now I heard from users that the page is not reachable anymore. I always can only fix this when I deactivate the plugin. So the Sync is now working, but the page stops working completely when the plugin is activated in the background?!

    Plugin Author schakko

    (@schakko)

    @florianbad Please check the error logs again. As I previously stated, there is no correlation between NADI’s “Sync to WordPress” feature and the SSO functionality.

    Thread Starter florianbad

    (@florianbad)

    @schakko
    Yes that is right. Right now I deactivated the SSO feature and this seems to work. Now the only thing is that he asks two times for a login and I guess thats because the SSO is not working.

    I guess I have to check the PHP log to see why the SSO is not working? Or should I find something in the NADI log?

Viewing 15 replies - 1 through 15 (of 16 total)
  • The topic ‘Worpress cannot operate anymore after activating NADI’ is closed to new replies.