Error 500 when adding Keycloak Open ID

Created on 13 March 2023, over 1 year ago
Updated 14 March 2023, over 1 year ago

After installing the OpenID Connect and Keycloak OpenID Copnnect modules, I want to add a Keycloak login service.

When navigating to admin/config/people/openid-connect/add/keycloak, I get a HTTP error 500. Anyone having this issue?

Drupal version: 10.0.3
OpenID Connect version: 3.0.0-alpha2
Keycloak OpenId Connect version: 2.2.0-beta5

🐛 Bug report
Status

Fixed

Version

2.2

Component

Code

Created by

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @robbe03
  • 🇧🇪Belgium BramDriesen Belgium 🇧🇪

    Quickly tested this and got following error:

    Fatal error: Declaration of Drupal\keycloak\Plugin\OpenIDConnectClient\Keycloak::defaultConfiguration() must be compatible with Drupal\openid_connect\Plugin\OpenIDConnectClientBase::defaultConfiguration(): array in /var/www/html/repos/keycloak/src/Plugin/OpenIDConnectClient/Keycloak.php on line 59

    Seems like something changed in the latest OpenID Connect Client Base.

  • @bramdriesen opened merge request.
  • 🇧🇪Belgium BramDriesen Belgium 🇧🇪

    Still some other things here to fix:

    Symfony\Component\Routing\Exception\MissingMandatoryParametersException: Some mandatory parameters are missing ("openid_connect_client") to generate a URL for route "openid_connect.redirect_controller_redirect". in Drupal\Core\Routing\UrlGenerator->doGenerate() (line 181 of core/lib/Drupal/Core/Routing/UrlGenerator.php).

  • Status changed to Needs work over 1 year ago
  • 🇧🇪Belgium BramDriesen Belgium 🇧🇪

    Credit for LudwigJP

  • Status changed to Fixed over 1 year ago
  • 🇧🇪Belgium BramDriesen Belgium 🇧🇪

    I fixed the errors here, would appreciate you testing the latest tagged release: 2.2.0-beta6

    I spotted a few more issues in other files, will work on those in separate issues, so it might be there is a higher beta when you come back to this.

    Please re-open or create a new ticket when you have tested it again.

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024