Weave Code
Runet Id Bundle Laravel Package
ruwork/runet-id-bundle
Symfony bundle for integrating Runet ID authentication into your application. It provides configuration and services to connect Runet ID accounts with Symfony security, enabling single sign-on and streamlined user login flows.
Ruwork Runet ID Bundle adds Runet ID authentication to Symfony applications. It provides ready-made Security bundle configuration for redirecting users to Runet ID and handling the callback, letting you add identity login without writing provider-specific glue code.
- Symfony Security integration with authenticator and user provider
- Redirect/callback authentication flow
- Configurable application credentials and redirect URI
- Automatic user mapping with optional first-login registration
- Extensible events for account linking and profile synchronization
Frequently asked questions about Runet Id Bundle
- Is ruwork/runet-id-bundle a Laravel package?
- No. It is a Symfony bundle for Runet-ID OAuth authentication, built around the Symfony Security component and dependency injection container. It has no Laravel service provider, guard, or Socialite driver, so it cannot be treated as a drop-in Laravel dependency.
- Can I install ruwork/runet-id-bundle in Laravel with Composer?
- Generally no. The package is pinned to 2018-era constraints, likely PHP 7.x with Symfony 3.4 or 4.0, so composer require will usually conflict with modern Laravel on PHP 8.1 and newer. Forcing it with --ignore-platform-reqs is not recommended because the Symfony wiring still does not fit Laravel.
- How do I add Runet-ID login to a Laravel application?
- Do not install the bundle directly. Clone the repository, audit the Runet-ID API client, DTOs, and token handling, then port that framework-agnostic logic into a first-party Laravel integration. A custom Socialite provider is usually the best path, with a custom guard only if Runet-ID session semantics differ from standard OAuth2.
- Does ruwork/runet-id-bundle include a Laravel Socialite provider?
- No. Socialite support is not part of the bundle. It exposes Symfony Security integration such as a runet_id firewall and authenticator plus an API client, so you would need to write the Socialite provider yourself using its endpoints, scopes, and claim mapping as a reference.
- Which Laravel and PHP versions does this package support?
- The package does not list Laravel support at all because it is a Symfony bundle. Its last release was 2018-08-20 with likely PHP 7.x and Symfony 3.4 or 4.0 constraints, so it predates modern Laravel versions. Check composer.json platform requirements before estimating any porting effort.
- Is ruwork/runet-id-bundle maintained and safe for production?
- Treat it as high risk. The upstream repository is archived, the last release was in 2018, and there is no maintainer, issue triage, or security response path. Identity and token-handling code with roughly seven years without patches should be reviewed as untrusted before any use.
- How do I configure Runet-ID OAuth credentials with this bundle?
- In Symfony, you would configure the bundle through its DI extension and services, then wire the runet_id firewall and authenticator. In Laravel there is no equivalent config file, so you would expose the client ID, secret, redirect URI, and scopes through config/services.php in your own Socialite provider.
- How do I map Runet-ID profiles to Laravel users?
- The bundle maps authenticated Runet-ID profiles to Symfony security users, and you must reimplement that mapping in Laravel. A typical approach is to store the Runet-ID subject identifier on your users table, then find or create a user in the Socialite callback and log them in. Consider PII and Russian 152-FZ data-residency requirements before storing profile data.
- What are Laravel-native alternatives to ruwork/runet-id-bundle?
- There is no known maintained Laravel package for Runet-ID in the provided context. The realistic alternatives are a custom Laravel Socialite provider, a direct OAuth2 client built on Laravel's HTTP client, or an official Runet-ID vendor SDK if one exists. Confirm the current Runet-ID API contract and sandbox access first.
- How should I test a Runet-ID OAuth integration in Laravel?
- Use Runet-ID sandbox credentials to validate scopes, token refresh, and profile claims during a short spike. In automated tests, fake the HTTP client and Socialite user responses so your callback, user mapping, and error handling are covered without calling the real identity provider. Also test failure paths for expired or revoked tokens.
Weaver
How can I help you explore Laravel packages today?