How thephpleague/oauth2-server-bundle works
OAuth2ServerBundle integrates League’s OAuth2 server with Symfony: clients initiate authorization, device-code, or token requests; the server validates and completes them, while bundle repositories and managers provide persistence. Symfony security authenticates resulting OAuth2 tokens and checks scopes. Client administration and key-management commands are additional product capabilities. The graph reflects the shown authorization and persistence calls plus README and service-configuration evidence; some controller and integration internals are represented only at their documented or configured boundaries.
Main entry points: AuthorizationController.php Authorization Flow · Manager Token and Client Managers · ClientManager.php Client Manager · Command Client Commands
Components 21
OAuth2 Protocol
- Authorization Flow
src/Controller/AuthorizationController.php - Device Flow
src/Controller/DeviceCodeController.php - Token Endpoint
src/Controller/TokenController.php - League OAuth Server
- Authorization Resolution
src/Event/AuthorizationRequestResolveEventFactory.php - User Conversion
src/Converter/UserConverterInterface.php
Persistence
- OAuth Repositories
src/Repository - Authorization Code Repository
src/Repository/AuthCodeRepository.php - Device Code Repository
src/Repository/DeviceCodeRepository.php - Token and Client Managers
src/Manager - Doctrine Managers
src/Manager/Doctrine - In-Memory Managers
src/Manager/InMemory - Doctrine Store
- Client Manager
src/Manager/Doctrine/ClientManager.php
Symfony Security
- OAuth2 Authenticator
src/Security/Authenticator/OAuth2Authenticator.php - Scope Checks
src/Security/EventListener/CheckScopeListener.php
Client Administration
- Client Commands
src/Command - Key Generation
src/Command/GenerateKeyPairCommand.php - Client Model
src/Model/AbstractClient.php - Client Save Event
src/Event/PreSaveClientEvent.php
Other components
- OAuth Client
Connections 20
- OAuth Client → Authorization Flow: requests authorization
src/Controller/AuthorizationController.php - Authorization Flow → League OAuth Server: validates and completes
src/Controller/AuthorizationController.php - Authorization Flow → Authorization Resolution: dispatches resolution
src/Controller/AuthorizationController.php - Authorization Flow → User Conversion: converts user
src/Controller/AuthorizationController.php - OAuth Client → Device Flow: requests device code
- OAuth Client → Token Endpoint: requests token
- Token Endpoint → League OAuth Server: handles token request
- League OAuth Server → OAuth Repositories: uses repositories
- League OAuth Server → Authorization Code Repository: uses code repository
- Authorization Code Repository → Token and Client Managers: reads and saves codes
src/Repository/AuthCodeRepository.php - Device Code Repository → Token and Client Managers: uses code managers
src/Repository/DeviceCodeRepository.php - Token and Client Managers → Doctrine Managers: implemented by
src/Manager/Doctrine/ClientManager.php - Token and Client Managers → In-Memory Managers: implemented by
config/services.php - Doctrine Managers → Doctrine Store: persists entities
- OAuth2 Authenticator → Scope Checks: checks scopes
- Client Commands → Client Manager: creates and manages
src/Command/CreateClientCommand.php - Client Commands → Client Model: builds client
src/Command/CreateClientCommand.php - Client Manager → Client Save Event: dispatches before save
src/Manager/Doctrine/ClientManager.php - Client Manager → Doctrine Store: persists clients
src/Manager/Doctrine/ClientManager.php - Key Generation → OAuth Client: generates server keys