I haven't tested with this setting as it was not available in earlier versiopns of pfSense but as a workaround you could setup AD-Access using a Radius-Server. See https://doc.pfsense.org/index.php/OpenVPN_with_RADIUS_via_Active_Directory for further details. That worked fine for me using passwords that didn't work using ldap.
Holger 2014-06-05 14:22 GMT+02:00 Jim Pingle <li...@pingle.org>: > On 6/5/2014 8:02 AM, Freund, Ingo wrote: > > today a user complained about not being able to login to IPsec VPN on > the pfSense via Shrew-Client 2.2.2 after he had changed his password. > > > > After some research and testing we have to report that passwords which > contain the paragraph sign 'ยง' are not validated the right way. > > The message on the DC is: Wrong username or password. > > After changing the paragraph sign into e.g. the dollar sign, everything > works fine. > > > > Is this a bug? > > Did you check "UTF8 Encode" on the LDAP server settings? > > If not, then such non-standard characters may not have been sent in the > proper format for the server to understand. > > Jim > _______________________________________________ > List mailing list > List@lists.pfsense.org > https://lists.pfsense.org/mailman/listinfo/list >
_______________________________________________ List mailing list List@lists.pfsense.org https://lists.pfsense.org/mailman/listinfo/list
