Skip to content
Snippets Groups Projects
Select Git revision
  • b9b92a27726890161db8af49c586d1160762aeb8
  • main default
  • keycloak-deprecate
  • remove-jwt-easy
  • ci-update
  • v0.1.15
  • v0.1.14
  • v0.1.13
  • v0.1.12
  • v0.1.11
  • v0.1.10
  • v0.1.9
  • v0.1.8
  • v0.1.7
  • v0.1.6
  • v0.1.5
  • v0.1.4
  • v0.1.3
  • v0.1.2
  • v0.1.1
  • v0.1.0
21 results

BearerUserProviderInterface.php

Blame
    • Reiter, Christoph's avatar
      3faa7dd5
      Switch to the OIDC discover protocol for the provider config · 3faa7dd5
      Reiter, Christoph authored
      The goal is to support every OIDC server that implements the discover
      protocol (Keycloak for example). This allows us to fetch all the required
      information at runtime without the user having to keep the settings
      in sync with the used server. The config and public keys are cached for
      one hour.
      
      While in theory this works with non-keycloak it isn't tested yet, and we
      still need keycloak specific settings for the API docs auth because we only
      support keycloak with our frontend web components which we inject into the
      openapi docs.
      
      Fixes #3
      3faa7dd5
      History
      Switch to the OIDC discover protocol for the provider config
      Reiter, Christoph authored
      The goal is to support every OIDC server that implements the discover
      protocol (Keycloak for example). This allows us to fetch all the required
      information at runtime without the user having to keep the settings
      in sync with the used server. The config and public keys are cached for
      one hour.
      
      While in theory this works with non-keycloak it isn't tested yet, and we
      still need keycloak specific settings for the API docs auth because we only
      support keycloak with our frontend web components which we inject into the
      openapi docs.
      
      Fixes #3
    BearerUserProviderInterface.php 326 B