• Resolved cwolff

    (@cwolff)


    We have set our environment to use port 389 and STARTTLS. We also have added the suffix of “@jis.org”.

    We are able to perform a successful “Test Authentication” from the test tool with either “myuser” or “[email protected]”.

    However, the same users are unable to login to the WordPress site? Also, nothing is written to the log file.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter cwolff

    (@cwolff)

    More Info:

    When logging in to the WordPress site, all users fail authentication with “ERROR: The password you entered for the username myuser is incorrect. Lost your password?”

    The same credentials are successful when attempted from the Next ADI test tool.

    I’m running into the same problem. Are you running a multisite? I’m finding that when I network activate the plugin and create the profile in the network admin panel certain options are not being carried down to the site level– namely the account suffix. When I network deactivated, and activated at the site level I could see those options weren’t set. Once I set them I was able to sign in correctly finally, but what a pain in the butt.

    In a multisite environment, the plugin will prefer the options from the site and not from the profile.

    For example:
    You create the profile P1, add the account suffix “@test.ad” and link this profile to the site S1.
    But in the configuration for the site S1, you add no account suffix (wordpress/s1/wp-admin/admin.php?page=next_ad_int_blog_options).
    When you try to login on S1, the plugin will use no account suffix.

    You can change this behavior in your profile options.
    Simply use a different “Manage permission” value for the option. Instead of “Blog admin sets the option value.” use “Deactivated and option value shown.”, “Deactivated and option value not shown.” or “Input field is invisible”.

    I think, the preference of the site options is not intuitive. We will discuss this problem internally.

    • This reply was modified 7 years, 10 months ago by tobi823.
    • This reply was modified 7 years, 10 months ago by tobi823.
    Thread Starter cwolff

    (@cwolff)

    My issue was related to a conflicting plugin. I use a plugin to theme login pages and it breaks Next ADi,

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Test authentication is successful, but users unable to log in to WordPress site’ is closed to new replies.