Opened 8 years ago
Closed 8 years ago
#1768 closed enhancement (fixed)
Add information about ASCII only character requirement to https://www.osgeo.org/cgi-bin/auth/ldap_edit_user.py
Reported by: | ehjuerrens | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | Unplanned |
Component: | SysAdmin | Keywords: | |
Cc: |
Description
The form available via
has certain requirements on the input that are not clearly stated on the page itself.
Please add something like "Please use only ASCII characters here!" to the fileds "Full name" and "Surname".
The problem is that if non ASCII characters are used, the following error message is displayed and the edit operation fails:
Traceback (most recent call last): File "/usr/lib/cgi-bin/auth/ldap_edit_user.py", line 207, in ldap_apply_user_info( userid, cn, sn, mail, password ) File "/usr/lib/cgi-bin/auth/ldap_edit_user.py", line 52, in ldap_apply_user_info l.modify_s( target, ml ) File "/usr/lib/python2.6/dist-packages/ldap/ldapobject.py", line 322, in modify_s return self.result(msgid,all=1,timeout=self.timeout) File "/usr/lib/python2.6/dist-packages/ldap/ldapobject.py", line 422, in result res_type,res_data,res_msgid = self.result2(msgid,all,timeout) File "/usr/lib/python2.6/dist-packages/ldap/ldapobject.py", line 426, in result2 res_type, res_data, res_msgid, srv_ctrls = self.result3(msgid,all,timeout) File "/usr/lib/python2.6/dist-packages/ldap/ldapobject.py", line 432, in result3 ldap_result = self._ldap_call(self._l.result3,msgid,all,timeout) File "/usr/lib/python2.6/dist-packages/ldap/ldapobject.py", line 96, in _ldap_call result = func(*args,**kwargs) INVALID_SYNTAX: {'info': 'cn: value #0 invalid per syntax', 'desc': 'Invalid syntax'} LDAP update has failed!
Attachments (2)
Change History (4)
by , 8 years ago
Attachment: | form_original.png added |
---|
comment:1 by , 8 years ago
See the attachment for the original and updated form as an example for a potential solution.
comment:2 by , 8 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
I've added the same <em>IMPORTANT</em> paragraph as the one found on the new user creation form. Thanks for spotting this.
Note:
See TracTickets
for help on using tickets.
Original form