We're updating the issue view to help you get more done. 

Ldap issue (search filter and '@' encoding) [patch]

Description

Today I've upgraded to Openfire 3.6.1 (previously 3.6.0a), but it seems that my open bugs are still unresolved (also checked with svn trunk update log).

See for reference my previous topics at:

Feel free to test my patches and integrate them in the next stable release

Environment

None

Acceptance Test - Entry

None

Activity

Show:
Guus der Kinderen
February 6, 2013, 7:57 PM

Removing the 'fix version' for all unresolved issues that were scheduled for version 7.8.2. We're releasing this version today - the remaining issues should be rescheduled later.

Daryl Herzmann
February 23, 2013, 1:32 PM

asked on forum if this issue is still valid

Daryl Herzmann
October 26, 2015, 2:08 PM

Speedy, you have thoughts on this?

speedy
November 5, 2015, 2:44 PM

it appears this has already been added some where down the line. The web interface will show users names escaped.

the current ldapmanager.java contains
// Add this to the result.
results.add(escapeJIDs ? JID.escapeNode(result) : result);

So I think this can be closed, however I did notice few issues in regards to usernames with special char like '@'. with the search plugin, and when adding an admin user in the setup wizard.

Guus der Kinderen
March 22, 2017, 9:59 PM

I can't reproduce a problem with the search plugin. The setup wizard stuff is addressed in https://github.com/igniterealtime/Openfire/pull/768

Fixed

Assignee

Guus der Kinderen

Reporter

Daryl Herzmann

Labels

None

Expected Effort

None

Ignite Forum URL

None

Fix versions

Priority

Major
Configure