How vouchedfor/tokenbundle works
This Symfony bundle exposes an external token encode/decode service: an application configures its endpoint, the bundle extension validates and loads configuration, and TokenEncoder sends encode and decode HTTP requests. The README documents bundle registration and endpoint configuration; the excerpts show configuration processing and the cURL calls. The services file exists in the tree but was not sampled, so its wiring to TokenEncoder is shown as unverified.
Main entry points: VouchedForTokenExtension.php Container extension · services.yml Service definitions · TokenEncoder.php Token encoder · VouchedForTokenBundle.php Bundle registration
Components 7
Symfony Bundle
- Bundle registration
VouchedForTokenBundle.php - Service definitions
Resources/config/services.yml
Configuration
- Container extension
DependencyInjection/VouchedForTokenExtension.php - Config schema
DependencyInjection/Configuration.php
Token Exchange
- Token encoder
Encoder/TokenEncoder.php
Other components
- Host application
- Token endpoint
Connections 6
- Host application → Bundle registration: registers
README.md - Host application → Container extension: configures URL
README.md - Container extension → Config schema: processes config
DependencyInjection/VouchedForTokenExtension.php - Container extension → Service definitions: loads services
DependencyInjection/VouchedForTokenExtension.php - Service definitions → Token encoder: registers
- Token encoder → Token endpoint: HTTP encode/decode
Encoder/TokenEncoder.php