How killmails/oauth2-eve works
A small PHP League OAuth 2.0 provider for EVE Online. The host application uses the League client and this provider for authorization-code login; the provider supplies EVE endpoints and converts the returned identity token into an EVE resource owner. Source is limited to the provider classes, so League internals and HTTP transport are represented only at the documented integration boundary.
Main entry points: EveOnline.php EVE provider · EveOnlineResourceOwner.php EVE resource owner
Components 7
OAuth integration
- League OAuth client
- EVE provider
src/Provider/EveOnline.php - EVE SSO
Identity mapping
- EVE JWKS
- JWT/JWK library
- EVE resource owner
src/Provider/EveOnlineResourceOwner.php
Other components
- Host application
Connections 9
- Host application → League OAuth client: uses
- League OAuth client → EVE provider: invokes provider
- EVE provider → League OAuth client: supplies endpoints
- League OAuth client → EVE SSO: authorization and token requests
- League OAuth client → EVE JWKS: fetches keys
- League OAuth client → EVE provider: passes token and keys
- EVE provider → JWT/JWK library: decodes token
- EVE provider → EVE resource owner: creates identity
- Host application → EVE resource owner: reads identity