TYPO3 Forger
  • Dashboard
  • Get involved
  • Reviews
    Overview Ready for review Work in progress Needs action Needs review Needs verification Needs rebase Negative votes Reviewed and verified Ready to merge
  • Issues
    Stale issues Possible duplicates By category By month
  • Sprints
    Overview Initiatives TYPO3 Core Review board
  • Tools
    Backports ReST helper
  • Help
  • Search
  • Login
Esc

Words find the open ones, a number the issue and the change with it.

  1. Issues
  2. #79566
Issue Bug Closed

#79566No login possible if cookie name is longer than 32 chars

Marco Huber 01/31/17, 11:28 updated 10/02/18, 11:02

Open in Forge Comment in Forge

Description

Because the cookie name is stored in the database be_sessions.ses_name (or fe_sessions.ses_name) and the field has a limit of 32 chars, the login does not work if the cookie name (set via $GLOBALS[‘TYPO3_CONF_VARS’][‘SYS|BE|FE’][‘cookieName’]) is longer.

Reviews 5

  • TYPO3_7-6 51539[BUGFIX] Limit primary key length on be_session and fe_session table Related to this issue Merged Christian Kuhn CR +2 V +2 → main, 7.6 Easy +2 −2 02/04/17, 16:38
  • main 51538[BUGFIX] Limit primary key length on be_session and fe_session table Related to this issue Merged Christian Kuhn CR +2 V +2 → 7.6 Easy +2 −2 02/04/17, 16:38
  • main 51537[BUGFIX] Limit primary key length on be_session and fe_session table Related to this issue Abandoned Christian Kuhn CR 0 V 0 → 7.6 Easy +2 −2 02/04/17, 15:45
  • TYPO3_7-6 51505[BUGFIX] Allow long cookie names Resolves this issue Merged Georg Ringer CR +2 V +2 → main, 7.6 Easy +2 −2 02/04/17, 12:11
  • main 51483[BUGFIX] Allow long cookie names Resolves this issue Merged Marco Huber CR +2 V +2 → 7.6 Easy +2 −2 02/02/17, 06:31

Related issues 1

  • Bug #79628Long primary index on be_session and fe_session table Related to Closed v8 Christian Kuhn 02/04/17, 13:58
Author
Marco Huber
Priority
Must have
TYPO3 version
7
© 2026 TYPO3 GmbH.
  • API
  • Privacy Policy
  • Legal Notice
  • Feedback