[Tickets #12041] Re: Authentication does not work any longer

[noreply at bugs.horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: http://bugs.horde.org/ticket/12041
------------------------------------------------------------------------------
  Ticket           | 12041
  Aktualisiert Von | martin.tessun at die-tessuns.de
  Zusammenfassung  | Authentication does not work any longer
  Warteschlange    | Horde Base
  Version          | 5.0.4
  Typ              | Bug
  Status           | Feedback
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


martin.tessun at die-tessuns.de (2013-02-14 20:17) hat geschrieben:

I found the problem (don't know where exactly it comes from):

horde_sessionhandler (description):
+----------------------+-------------+------+-----+---------+-------+
| Field                | Type        | Null | Key | Default | Extra |
+----------------------+-------------+------+-----+---------+-------+
| session_id           | varchar(32) | NO   | PRI | NULL    |       |
| session_lastmodified | int(11)     | NO   | MUL | NULL    |       |
| session_data         | blob        | YES  |     | NULL    |       |

As you can see, the session_id has 32 characters. The id generated is  
longer :)

E.g.:
Session-ID:   jiah80ekjoqbu0ccmrujkoluqpsqkjhpv60vg8dv001v4l5v6341
in Database: jiah80ekjoqbu0ccmrujkoluqpsqkjhp

So I extended the session_id to 64 Chars. Now it looks like this:
+----------------------+-------------+------+-----+---------+-------+
| Field                | Type        | Null | Key | Default | Extra |
+----------------------+-------------+------+-----+---------+-------+
| session_id           | varchar(64) | NO   | PRI |         |       |
| session_lastmodified | int(11)     | NO   | MUL | NULL    |       |
| session_data         | blob        | YES  |     | NULL    |       |
+----------------------+-------------+------+-----+---------+-------+

And now it is working again.