Opened 2 years ago

Closed 2 years ago

#1487681 closed Bugs (wontfix)

Problems with uppercase characters in users.username in db and case-insensitive logins

Reported by: samuel Owned by:
Priority: 5 Milestone: 0.6-beta
Component: Core functionality Version: 0.5
Severity: normal Keywords:
Cc:

Description

I have a user who used a login with uppercase characters at his first time login in roundcube some time ago with a older version of roundcube. In the database in the table users his username also has this uppercase characters. After upgrading to version 0.5 of roundcube he was not able to login anymore because the login seems now to be case-sensitive. Changing $rcmail_config['login_lc'] to true does not help at this point because the username string in database will not be converted to lowercase character. I use e-mail addresses as login and a mysql database.

Steps to reproduce:

  • change a character of your username to uppercase in database in table users
  • set $rcmail_config['login_lc'] to true in the config
  • try to login

Workaround: Convert all usernames in your database in table users to lowercase.

Change History (3)

comment:1 Changed 2 years ago by alec

  • Milestone changed from later to 0.6-beta

I think we'll not fix this. Use your workaround and forget.

comment:2 Changed 2 years ago by charly

Let me understand:

  • If a new user logs into the new RC, there will be no error.
  • The error occurs if an older user, from an older version of RC, has typed his username with wrong case, then after upgrading RC to the latest version there are case problems.

If i understand correctly, to "fix" this bug we need to write some lines documenting this behavior into KnownIssues and Upgrade wiki pages and into the TXTs distributed with RC.

I don't agree to change any line of code; may be provide a sample sql command or somethin in the Documentation.

comment:3 Changed 2 years ago by alec

  • Resolution set to wontfix
  • Status changed from new to closed

Added comment in config file and wiki.

Note: See TracTickets for help on using tickets.