Tickets :: [#8531] Configuration doesn't warn about non-alphanumerics in session name.

Summary	Configuration doesn't warn about non-alphanumerics in session name.
Queue	Horde Base
Queue Version	3.3.4
Type	Bug
State	Not A Bug
Priority	1. Low
Owners
Requester	rpjday (at) crashcourse (dot) ca
Created	08/27/2009 (5801 days ago)
Due
Updated	08/30/2009 (5798 days ago)
Assigned
Resolved	08/30/2009 (5798 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

08/30/2009 12:17:12 PM	Jan Schneider	Comment #2 State ⇒ Not A Bug	Reply to this comment
There already is a description in the interface saying exactly this.

08/27/2009 10:56:58 AM	rpjday (at) crashcourse (dot) ca	Comment #1 State ⇒ Unconfirmed Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ Configuration doesn't warn about non-alphanumerics in session name. Queue ⇒ Horde Base Milestone ⇒ Patch ⇒ No	Reply to this comment
Apparently, when configuring a 3.3.4 Horde install, using a session name of "Horde-3.3.4" causes problems with PHP (because of non-alphanumerics in the session name), which then causes all attempts to log in to be quietly verified, then dropped. There is no apparent warning that this is happening, and no apparent subsequent diagnostics during those failed login attempts. It might be useful for the configuration to either warn the user about non-alphanumerics in the session name, or just reject such names outright. Switching to the session name of "Horde334" caused logins to start working again.