Weave Code
Oauth User Data Laravel Package
concrete5/oauth-user-data
Integrates OAuth user data into Concrete CMS, letting sites authenticate via external providers and map returned profile details to user accounts. Helps streamline registration and login by syncing names, emails, and related attributes from OAuth responses.
concrete5/oauth-user-data is a Concrete CMS (concrete5) package that retrieves and maps user profile data from OAuth providers such as Google, Facebook, and other compatible identity services. It lets you populate and refresh Concrete user attributes—name, email, avatar, and custom fields—directly from the provider's response during login or registration.
- Authenticates against multiple OAuth 2.0 providers
- Maps remote profile fields to Concrete user attributes
- Syncs data on login or first-time registration
- Configurable field mappings and provider credentials
- Lightweight integration with the Concrete CMS user system
Frequently asked questions about Oauth User Data
- Is concrete5/oauth-user-data compatible with Laravel?
- No. It is a concrete5-specific fork of an extension to Lusitanian/PHPoAuthLib and has no Laravel service provider, configuration conventions, facade, or framework integration. For Laravel, use Socialite with a small internal profile-normalization layer instead.
- Can I install concrete5/oauth-user-data in a Laravel app via Composer?
- It may install if the dependency graph resolves, but you should treat it as vendoring legacy code rather than adopting a maintained dependency. The last release was 2017-10-29, and it likely conflicts with modern PHP, Laravel, Guzzle, and PSR versions. Audit composer.json and transitive dependencies before any spike.
- What Laravel package should I use instead for OAuth user profiles?
- Use Laravel Socialite plus provider-specific drivers, backed by a small internal normalization layer for profile fields. That keeps OAuth tokens and personal data inside Laravel’s normal auth architecture. Socialite is the preferred path for new Laravel work.
- Does concrete5/oauth-user-data support Laravel Socialite or Laravel service providers?
- No. The package is built for concrete5 integration and does not provide Socialite drivers, Laravel service providers, facades, or framework configuration. Any Laravel integration would sit outside the framework’s normal auth flow.
- Which OAuth providers does concrete5/oauth-user-data support?
- It extends Lusitanian/PHPoAuthLib to extract and map user profile data, so provider support depends on that library and the concrete5 fork. Check the repository and composer.json for the exact providers and profile fields covered. Do not assume it covers providers that Laravel Socialite already handles.
- Is concrete5/oauth-user-data maintained and safe for production?
- It is effectively unmaintained: the repository has 0 stars, 0 dependents, and its last release was in 2017. Risks include abandoned upstream dependencies, outdated OAuth provider behavior, PHP 8+ incompatibility, Guzzle/PSR conflicts, and no security patch cadence. OAuth profile extraction is security-sensitive because it handles tokens and personal data, so adopting it shifts maintenance and security review in-house.
- How do I migrate from concrete5/oauth-user-data to Laravel Socialite?
- Inventory the OAuth providers and profile fields you currently expect, then map each provider to a Socialite driver or direct OAuth client. Extract only the normalization rules from this package, rewrite them behind an internal interface, and run old and new profile extraction in parallel for validation. Port only the required provider mappings under MIT attribution, add contract tests, canary the replacement, and then remove the legacy package.
- Can I reuse the provider mappings or extractor logic in a Laravel adapter?
- Yes, the MIT-licensed code can be copied into an internal Laravel adapter instead of installed as a runtime dependency. Port only the provider field mappings or extractor logic that is uniquely useful, and add attribution. Cover token handling, profile normalization, error paths, and provider API changes with contract tests.
- What PHP, Laravel, or Guzzle versions does concrete5/oauth-user-data require?
- Exact version constraints are not stated in the provided context, so audit composer.json and transitive dependencies before any compatibility spike. Expect friction with modern PHP and Laravel versions, PSR interfaces, Guzzle, and Lusitanian/PHPoAuthLib. Pin versions only inside an isolated legacy service if absolutely necessary.
- Are there alternatives to concrete5/oauth-user-data for Laravel OAuth authentication?
- Yes. Laravel Socialite with provider-specific drivers is the primary alternative, optionally supplemented by direct OAuth clients or an internal extractor adapter. If you need only provider field mappings, port the MIT-licensed logic into a Laravel-native normalization layer. Avoid introducing the legacy package into a clean Laravel application without a proven compatibility matrix.
Weaver
How can I help you explore Laravel packages today?