LDAP auth should check for invalid utf8 characters in names

Bug #650678 reported by Richard Mansfield
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mahara
Fix Released
Low
François Marier
Tags: ldap
Changed in mahara:
status: New → Triaged
importance: Undecided → Low
milestone: none → 1.4.0
Revision history for this message
Iñaki Arenaza (iarenaza) wrote :

We should also set the default LDAP version to '3' in the configuration settings page.

Some LDAP servers refuse v2 connections by default (e.g., OpenLDAP 2.x and later) and using v3 makes the server use utf8 both in the queries and the responses (unless the server is really broken).

Setting the default to v3 would ensure that nobody forgets to select v3 and gets a broken setup that works most of the time (but not always).

Saludos.
Iñaki.

tags: added: ldap
Changed in mahara:
milestone: 1.4.0 → none
Revision history for this message
François Marier (fmarier) wrote :

3 was made the default in f36a3108d662b2802f31affe3cea3397b984de2a to fix bug #724060

The user's personal details are now sanitized in the same way as in the "add user" admin page.

Changed in mahara:
status: Triaged → Fix Committed
Revision history for this message
François Marier (fmarier) wrote :

See bug #888840 for the sanitization changes (46189cc1f8665017f112ce6de3b99f5a70a4b19a)

Changed in mahara:
status: Fix Committed → Fix Released
status: Fix Released → Fix Committed
milestone: none → 1.5.0
assignee: nobody → François Marier (fmarier)
Melissa Draper (melissa)
Changed in mahara:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.