Worpress cannot operate anymore after activating NADI

  • Resolved florianbad

    (@florianbad)


    3 years, 10 months ago

    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 16 replies (of 16 total)
  • Plugin Author schakko

    (@schakko)

    You’ll have to check both logs.

    – 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.

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