heiglandreas

The version 2.5.6 should fix your issues. Thanks for reporting and thanks for the patience!

I’m sorry for the inconvenience. I am working on a fix right now.

Until tthat is finished, you can install the 2.5.3 version (or any other previous version) by downloading the zip archive on the github release page and install that package

Hey there.

Thanks for the suggestion. You can always open a PR on github (https://github.com/heiglandreas/authldap) for modifications. ??

I’ll implement that within the next few days. Expect a PR in the near future.

Nope. That does not work with this plugin. Users will be able to use the same username and password as with their Windows Login. But they will still have to log in.

Depends on what your understanding of SSO and your SSO-Provider is.

When you use LDAP as an SSO provider (And that includes ActiveDirectory, but not AzureActiveDirectory) you can use this plugin to have SSO.

When you use fore example SAML or OKTA or Authy or some similar service, then that will not work with this plugin.

Does that answer your question

Well. What shall I say.

The error message states the issue. The PHP-backend that runs the code needs the LDAP-Extension to be able to communicate with your LDAP-Server.

So you will need to install that extension on your local webserver. How that is done depends on so many factors that your best bet would be to use your favourite search engine to find how to install the ldap-extension on your setup.

And this message is not an error but a notice. You can configure the plugin but without the LDAP-Extension the plugin will not be able to actually *do* anything.

Cheers

Andreas

Hey.

There are two ways to disable the ldap authentication. One is by renaming the plugin folder. That will disable the plugin and then you can at least use your blog again.

The other way is a bit more complex as all config options are within the options-table (most probably “wp_options” in your DB) as json encoded value to the key “authLDAPOptions”. There is a flag “Enabled” that you should set to “false” to disable the authentication while still having the plugin enabled.

Eigentlich sollte es keine Probleme nach einem Update geben. Das Plugin ist bis PHP8.0 getestet.

Wenn allerdings die LDAP-Extension nach dem Update nicht mehr verfügbar ist, kann das Plugin allerdings nicht mehr funktionieren. Das ist die einzige Erkl?rung, die ich so spontan habe. Wenn das nicht das Problem ist, dann bitte die gesamte Fehlermeldung inklusive Stack-Trace posten.

Can you provide me with your (sanitized) configuration? Screenshot to andreas AT heigl DOT org would be awesome!

Also the output of the Webservers error-log after activating the debugging on authLdap and trying to log in.

@lamtiman: Do you have any issues with the plugin in WordPress 5.7.2?

And if so: Would you mind opening up a new thread then?

• This reply was modified 3 years, 5 months ago by heiglandreas.

If you are only using one LDAP-Server you will not need the URL-Separator.

The main points are the LDAP-URI, confirming or adapting the user and group-settings (they usually work with OpenLDAP. If you are using ActiveDirectory those need tweaking) and depending opn whether you want to use the group feature, the group-roles mapping is important.

Feel free to send me a (sanitized, I don’t need passwords) screenshot of your config as well as an excerpt of the log files (make sure to activate the debugging flag) to authldap AT heigl DOT org and I’ll see what I can find ??

Hey there.

I’m not doing remote sessions for setup as I don’t have the time for that. The Settings screen has a lot of information and feel free to drop any specific questions here and I’ll see to it that I answer them

Hey. Due to health issues I won’t be able to dig into this any deeper before the 6th of April.

Meanwhile you could ask your AD Administrators whether they can give you more information on whether that URI is plausible from their side

Cheers

You are welcome. Anything else that needs fixing? ??

The most interesting question is why the user is identified as not being available within wordpress. Did the username change?