Weave Code
Odnoklassniki Laravel Package
socialiteproviders/odnoklassniki
Odnoklassniki (OK.ru) OAuth2 provider for Laravel Socialite. Adds a ready-made driver so you can authenticate users via Odnoklassniki with one line: Socialite::driver('odnoklassniki')->redirect(). Install with Composer, set your client ID and secret, and receive standard Socialite user objects.
Odnoklassniki is a community provider that adds OAuth authentication for the Russian social network Odnoklassniki to Laravel Socialite. Install via Composer, register the service provider and event listener, then authenticate with the familiar Socialite::driver('odnoklassniki') API.
- Drop-in driver for Socialite with a standard redirect/callback flow
- Retrieves user ID, name, and profile data via Odnoklassniki's REST API
- Handles Odnoklassniki's signature-based request signing
- Configurable client ID, client secret, and redirect URI
- Works with the wider
socialiteprovidersecosystem
Frequently asked questions about Odnoklassniki
- How do I install the Odnoklassniki provider for Laravel Socialite?
- Install it with composer require socialiteproviders/odnoklassniki, then follow the Socialite Providers registration steps for your Laravel version. Typically that means registering the package's SocialiteWasCalled listener, adding an odnoklassniki block to config/services.php, and redirecting with Socialite::driver('odnoklassniki')->redirect(). Check the composer.json illuminate constraints first so you do not install a version your Laravel release cannot resolve.
- Which Laravel versions does socialiteproviders/odnoklassniki support?
- The provided metadata does not state a Laravel version range, so read the require block in composer.json for illuminate/support constraints and run composer why-not socialiteproviders/odnoklassniki with your Laravel version. The 4.1.0 note only confirms PHP 8 support, which is not the same as confirmed Laravel 9 or Laravel 10 support.
- How do I configure Odnoklassniki (OK.ru) credentials in Laravel?
- Add an odnoklassniki entry to config/services.php containing client_id, client_secret, and redirect, and source those values from environment variables rather than hard-coding them. The redirect URI must exactly match the callback URL registered in your OK.ru application. Then use Socialite::driver('odnoklassniki') in your login and callback routes.
- How do I redirect users to OK.ru and handle the callback with Socialite?
- Send users to Socialite::driver('odnoklassniki')->redirect() from your login route. In the callback route, call Socialite::driver('odnoklassniki')->user() to retrieve the Socialite user, then create or match your local user record. Handle denied consent, invalid state, and provider errors explicitly before treating the login as successful.
- Does this package work with PHP 8, PHP 8.1, and PHP 8.2?
- Version 4.1.0 added PHP 8 support, but that note is ambiguous: it may mean a widened composer constraint, CI coverage, or actual fixes. Check the exact PHP constraint and CI matrix, then run the package tests and a sign-in smoke test on your production PHP version. PHP 8.0 compatibility does not automatically prove clean behavior on PHP 8.1 or 8.2, where deprecations can surface.
- How can I test Odnoklassniki Socialite login without hitting the real OK.ru API?
- Use Http::fake to stub the token and user-profile endpoints, or mock the Socialite driver, then assert the redirect URL and callback behavior. Keep live OK.ru calls out of CI and add failure cases such as denied consent, invalid state, and API errors. This lets you test your application's user-matching logic without depending on an external service.
- What should I check before using this package in production?
- Verify the composer constraints and review the lockfile diff before merging, keep client_secret in environment variables, enforce HTTPS on the redirect URI, and validate OAuth state. Add error handling for token expiry and API failures, then run a staging smoke test through the real sign-in path. Do not treat a minor PHP 8 support release as proof that every production path has been exercised.
- How do I add a custom Socialite provider if this Odnoklassniki package is incompatible?
- If the package's illuminate constraints exclude your Laravel version, implement a custom provider by extending Laravel Socialite's AbstractProvider or use league/oauth2-client with a custom provider. Implement the authorization URL, token exchange, and user mapping for OK.ru, then register it with Socialite::extend. That gives you control, but you own token refresh, error handling, and tests.
- Is socialiteproviders/odnoklassniki maintained and safe to use?
- Check the socialiteproviders/providers monorepo for recent commits, release notes, CI matrix, and open issues rather than relying on the package name alone. Because 4.1.0 is a minor release that added PHP 8 support, inspect whether source changed or only constraints and CI were updated. Pin a version you have tested and review its diff before deployment.
- What is the difference between socialiteproviders/odnoklassniki and writing my own OK.ru OAuth client?
- The package supplies a drop-in Socialite driver, so you use Socialite::driver('odnoklassniki') and the familiar redirect and user flow with less custom code. A custom client gives you full control over endpoints, scopes, and refresh logic, but you maintain it and must test against OK.ru yourself. Choose the package when its Laravel and PHP constraints match your stack, and the custom route when they do not.
Weaver
How can I help you explore Laravel packages today?