Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • T typo3.org
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 85
    • Issues 85
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 7
    • Merge requests 7
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • services
  • t3o sites
  • typo3.org
  • typo3.org
  • Issues
  • #621

Closed
Open
Created Apr 12, 2022 by Oliver Hader@ohaderContributor0 of 1 task completed0/1 task

HTTP 503 Error during frontend login

Summary

Internal Server Error (HTTP 503) after login via Keycloak (my.typo3.org).

Steps to reproduce

(How one can reproduce the issue - this is very important)

Example URL

https://typo3.org/oauth2/callback?oauth2-provider=keycloak&logintype=login&state=[redacted] (not directly applicable, use the login mechanism via my.typo3.org instead)

What is the current bug behavior?

HTTP 503 Error Status Code

What is the expected correct behavior?

Login via my.typo3.org works, session is created, user is redirected back to regular typo3.org site.

Acceptence Criterias

  • frontend login via my.typo3.org must be possible

Relevant logs and/or screenshots

Oops, an error occurred! Event: 3b0513a96ddb463b89e6e0770d368df7
Return value of T3o\T3olayout\Provider\Typo3ResourceOwner::getId() must be of the type int or null, string returned

Screen_Shot_2022-04-12_at_08.24.15

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Assignee
Assign to
Time tracking