Openfire

JDBC Auth Provider accepts now also unencoded JIDS

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: Database
  • Labels:
    None
  • Acceptance Test - Add?:
    No

Description

It seems that the JDBC auth provider looks for escaped JIDs in remote databases.
So a user "John Miller" can never be authenticated using this auth provider. It would need to change it's account to "John\20Miller" which is usually not possible.

Add a switch/system property to enable the usage of unencoded JIDs.

Activity

Hide
Permalink
LG added a comment -

Add another switch to allow "John Miller". Currently /src/java/org/jivesoftware/openfire/auth/JDBCAuthProvider.java uses
"98: username = username.trim().toLowerCase();" so the user name must be stored as "john miller".
So one should have the option to use
"98: username = username.trim();" without toLowerCase().

Show
LG added a comment - Add another switch to allow "John Miller". Currently /src/java/org/jivesoftware/openfire/auth/JDBCAuthProvider.java uses "98: username = username.trim().toLowerCase();" so the user name must be stored as "john miller". So one should have the option to use "98: username = username.trim();" without toLowerCase().

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
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.