Extension talk:LDAP Authentication/Configuration Options

Custom LDAP configuration options ($wgLDAPOptions)
After getting the two messages for onle one option set: 1.2e Can't set option to LDAP! Option code and value: 0=4 1.2e Can't set option to LDAP! Option code and value: 1=120 I realised that $wgLDAPOptiosn is an array and the option is read via constant, so the exmample should read and so it worked for me ---Venia 08:08, 26 May 2011 (UTC)

P.S. Nevertheless it worked like charm on Windows Server 2008 R2 using IIS 7.5

Multiple domains that will be using auto authentication ($wgLDAPAutoAuthDomain)
Dealing with different AD directory servers for the domains using REMOTE_USER. Please watch the three backslashes and define your domains lowercase. ---Venia 09:06, 26 May 2011 (UTC)

Option on single domain systems for no domain menu
It would be nice to be able to turn off the domain menu on login if you only have one domain to select from.--Pashdown (talk) 18:02, 3 December 2012 (UTC)

Can the Special:ChangePassword be disabled?
Because my LDAP is read-only to the wiki, I'd like to be able to remove the Special:ChangePassword page. Is there a way to do this with an option to the extension?

OpenLDAP & Ubuntu 12.04 LTS
On OpenLDAP this will always fail with message "Failed to bind". This won't work. Evar.

Config Equivalency Between This LDAP ext and the Apache Auth Provider "ldap"
I just thought I would show an equivalent configuration for this extension that matches the same ldap configuration we use in apache httpd.

I've replaced sensitive info with substitutions

The apache config:

The MW Ldap authentication extensions config:

Cheers, Kyle 142.166.3.43 11:41, 4 April 2013 (UTC)

Setting for IBM Lotus Domino 8.5 LDAP
This is the setting which can make my wiki works properly with ldap server .It cost me several days.The point is "$wgLDAPProxyAgent" only need values for CN & O, dosen`t need value for OU and DC.

Willemzhai (talk) 08:05, 17 March 2015 (UTC)

Server names in SSL Cert?
Hi There,

I've got authentication to AD working in cleartext, but am having a lot of trouble connecting over SSL.

As per the guidance below, it looks like my wgLDAPServerNames values must somehow correlate to values retrieved from my domain controller with the openssl s_client -showcerts -connect command? Unfortunately I do not see any server names referenced in my retrieved cert, and the Acceptable client certificate CA names list does not include server names either. Can you clarify this point a bit more?

If you are going to use SSL or StartTLS, it is important that the server names provided here exactly match the name provided by the SSL certificate returned by the server; otherwise, you may have problems.