Download the PHP package e4se/laravel-telegram-oidc without Composer
On this page you can find all versions of the php package e4se/laravel-telegram-oidc. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Informations about the package laravel-telegram-oidc
OpenID Telegram Connect (OIDC) Provider for Laravel Socialite
Installation & Basic Usage
Please see the Base Installation Guide, then follow the provider specific instructions below.
This provider implements Telegram's current OpenID Connect login flow documented at core.telegram.org/bots/telegram-login.
Telegram setup
Before configuring Laravel, make sure your bot is prepared in Telegram:
- Open
@BotFatherand navigate toBot Settings > Web Login - Register every allowed website origin and callback URL you plan to use
- Copy the
Client IDandClient Secretshown by BotFather
Telegram only accepts login requests and redirects for pre-registered URLs.
Add configuration to config/services.php
Add provider event listener
Configure the package's listener to listen for SocialiteWasCalled events.
Laravel 11+
In Laravel 11, the default EventServiceProvider provider was removed. Instead, add the listener using the listen method on the Event facade, in your AppServiceProvider boot method.
Laravel 10 or below
Add the event to your listen[] array in app/Providers/EventServiceProvider. See the Base Installation Guide for detailed instructions.
Usage
You should now be able to use the provider like you would regularly use Socialite (assuming you have the facade installed):
By default the provider uses PKCE (S256) and validates the returned id_token against Telegram's JWKS,
including iss, aud, and exp, as required by the official documentation.
Returned User fields
idnamenicknameavatar
More fields are available under the user subkey:
Telegram returns user claims directly in the id_token. Telegram does not currently expose a separate
userinfo endpoint, so this provider reads the authenticated user from the validated ID token instead.
Customizing the scopes
You may extend the default scopes (openid profile) by adding a scopes option to your OIDC service
configuration and separate multiple scopes with a space. Telegram currently documents phone and
telegram:bot_access as additional available scopes:
PKCE
PKCE is enabled by default to match Telegram's recommended authorization code flow. If you need to disable it for compatibility testing, you can do so explicitly:
Proxy and HTTP timeouts
You may route Telegram OIDC requests through a proxy directly from the provider config:
For advanced transport customization you can still pass raw Guzzle options via guzzle. Explicit guzzle options take precedence over the top-level proxy, connect_timeout, and timeout keys:
Based on the work of Kovah
All versions of laravel-telegram-oidc with dependencies
ext-json Version *
socialiteproviders/manager Version ^4.0
illuminate/http Version ^9.0 | ^10.0 | ^11.0 | ^12.0
illuminate/support Version ^9.0 | ^10.0 | ^11.0 | ^12.0
firebase/php-jwt Version ^6.4|^7.0