Openfire (ARCHIVED)

Fix LDAP ou="... ..." (%20) problem in baseDN

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.6.2
  • Fix Version/s: 3.4.5
  • Component/s: Core
  • Labels:
    None
  • Environment:

    LDAP

  • Acceptance Test - Add?:
    No

Description

One can not login if the ou contains spaces like "<baseDN>OU=My Users;DC=domain;DC=net</baseDN>" while My_Users works fine.

References:
http://www.jivesoftware.org/community/thread.jspa?threadID=18805
http://www.jivesoftware.org/community/thread.jspa?threadID=19988

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
LG added a comment -

JM-695 describes similar problems with /, ! and , so one may want to fix and test it alltogether.

Show
LG added a comment - JM-695 describes similar problems with /, ! and , so one may want to fix and test it alltogether.
Hide
Permalink
Matt Tucker added a comment -

I don't have a good way to duplicate this issue at the moment so I'm pushing to a future release. It would be helpful if someone could verify if this is still an issue. If it is an issue, the following might help:

http://java.sun.com/products/jndi/tutorial/beyond/names/syntax.html

Show
Matt Tucker added a comment - I don't have a good way to duplicate this issue at the moment so I'm pushing to a future release. It would be helpful if someone could verify if this is still an issue. If it is an issue, the following might help: http://java.sun.com/products/jndi/tutorial/beyond/names/syntax.html
Hide
Permalink
Denis Golovan added a comment -

Confirm, v3.3.1 still has the issue. Besides, when ou has international symbols (such as Russian ones ) wildfire.xml saves it incorrectly both from admin console and when updating wildfire.xml during the work. Correcting manually (using Win1251 codepage, AFAIK utf-8 allows this) helps a bit, some time after server rewrites my ou name and stops authentificating users.

Show
Denis Golovan added a comment - Confirm, v3.3.1 still has the issue. Besides, when ou has international symbols (such as Russian ones ) wildfire.xml saves it incorrectly both from admin console and when updating wildfire.xml during the work. Correcting manually (using Win1251 codepage, AFAIK utf-8 allows this) helps a bit, some time after server rewrites my ou name and stops authentificating users.
Hide
Permalink
Denis Golovan added a comment -

Besides, I discover another strange behaviour - each time after config being rewritten by the server, international symbols (such as Russian ones ) are converted in presentation (in utf-8, I guess) which doubles in length. Such things happen even with text in comments. Maybe some bugs in java xml parser?

Show
Denis Golovan added a comment - Besides, I discover another strange behaviour - each time after config being rewritten by the server, international symbols (such as Russian ones ) are converted in presentation (in utf-8, I guess) which doubles in length. Such things happen even with text in comments. Maybe some bugs in java xml parser?
Hide
Permalink
Daniel Henninger added a comment -

The hardest part of this is setting up a quick LDAP server that has spaces like this. And maybe even some Russian character ones, but honestly, I think whatever fix I put in place for one will fix the other. Going to set up a quick virtual environment to test this with. Shouldn't be hard.

Show
Daniel Henninger added a comment - The hardest part of this is setting up a quick LDAP server that has spaces like this. And maybe even some Russian character ones, but honestly, I think whatever fix I put in place for one will fix the other. Going to set up a quick virtual environment to test this with. Shouldn't be hard.
Hide
Permalink
Daniel Henninger added a comment -

Related to this, looks like a number of HTML characters are converted improperly when saving LDAP filter changes. & -> & for example

Show
Daniel Henninger added a comment - Related to this, looks like a number of HTML characters are converted improperly when saving LDAP filter changes. & -> & for example
Hide
Permalink
Chris Hirsch added a comment -

This issue is still present in 3.5.1. If I change my uid to be mail it will change the @ sign to an HTML char and not authenticate the user because it can't find it.

Show
Chris Hirsch added a comment - This issue is still present in 3.5.1. If I change my uid to be mail it will change the @ sign to an HTML char and not authenticate the user because it can't find it.

People

Vote (3)
Watch (4)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for igniterealtime.org. Try JIRA - bug tracking software for your team.