Weave Code
Appnet Laravel Package
socialiteproviders/appnet
App.net OAuth provider for Laravel Socialite. Adds App.net login to your Laravel app via the SocialiteProviders manager, letting you authenticate users with their App.net accounts through a simple, consistent driver alongside your other providers.
App.net OAuth2 Provider for Laravel Socialite
Frequently asked questions about Appnet
- What is socialiteproviders/appnet and what does it do?
- socialiteproviders/appnet is a Laravel Socialite OAuth 2.0 provider adapter for App.net. It extends the SocialiteProviders manager flow, declares App.net authorization and token endpoints, and maps the returned profile to a standard Socialite user object with ID, username, name, and avatar. It is a thin provider package, not a full authentication system, and it is distributed as a read-only subtree split of the SocialiteProviders/Providers monorepo.
- How do I install socialiteproviders/appnet in Laravel?
- Install it with Composer by running composer require socialiteproviders/appnet. Then register the SocialiteProviders manager service provider and add the AppNetExtendSocialite listener to the SocialiteWasCalled event, following the SocialiteProviders convention. After that, add your client ID, client secret, and redirect URI to config/services.php and call Socialite::driver('appnet').
- How do I configure App.net credentials for Laravel Socialite?
- Add an appnet block to config/services.php with client_id, client_secret, and redirect values, typically sourced from environment variables. The redirect URI must match the callback URL registered with App.net exactly. Then use Socialite::driver('appnet')->redirect() for the authorization redirect and handle the callback with Socialite::driver('appnet')->user().
- Which Laravel and PHP versions does socialiteproviders/appnet support?
- Release 4.1.0 adds PHP 8 support, and the package is built for Laravel applications using Socialite and the SocialiteProviders manager. The changelog is a single compatibility line, so it does not clarify whether the CI matrix covers PHP 8.2 or 8.3; confirm against composer.json and the parent monorepo before relying on a specific version. Laravel version support is inherited from Socialite and the manager package rather than defined by this provider.
- How do I use Socialite::driver('appnet') to log in users?
- Register the provider listener, then call Socialite::driver('appnet')->redirect() to send the user to App.net's authorization endpoint. In your callback route, call Socialite::driver('appnet')->user() to exchange the code and retrieve the Socialite user object. From there you can log the user in or create a local account using the returned ID, username, name, and avatar.
- Does App.net OAuth still work in 2024 or 2025?
- No. App.net shut down in 2017, and this package still hardcodes the app.net and account.app.net OAuth endpoints. You can install it and unit-test it against mocks, but it cannot authenticate a real user because the upstream service no longer issues tokens. Treat it as a legacy adapter unless you have a live, first-party App.net-compatible endpoint and control the domain.
- Can I test the App.net Socialite provider without a real App.net account?
- You can test the provider flow by mocking Socialite or the underlying HTTP client and returning a fake token and user payload. The package itself has no database, migration, or queue surface, so tests focus on the redirect, callback, and user-mapping path. End-to-end testing against App.net is not possible because the service is defunct.
- Is it safe to use socialiteproviders/appnet in production?
- Using it in production is not recommended for real App.net authentication because the service is dead and the endpoints are hardcoded. There is also supply-chain risk: if app.net or account.app.net domains lapse or are repurposed, OAuth redirects and client credentials could be exposed to a third party. Storing or transmitting credentials to a defunct host is likely to be an audit finding, and PHP 8 support alone does not address that.
- What are alternatives to socialiteproviders/appnet for Laravel social login?
- For active social login, use a maintained Socialite provider for a live identity provider such as GitHub, Google, or Facebook, or write an in-house Socialite provider for your target service. An in-house App.net-compatible provider is roughly 100 lines if you actually have a live endpoint. If you only need to retain historical App.net user records, an OAuth provider is unnecessary; keep the records and skip the login flow.
- How is socialiteproviders/appnet maintained and what changed in 4.1.0?
- The package is a generated read-only split of the SocialiteProviders/Providers monorepo, so fixes must land upstream and be re-split. Release 4.1.0 was a monorepo-wide PHP 8 compatibility bump, not provider-specific work, and the changelog does not show endpoint, scope, or user-mapping changes. With zero stars and zero dependents, there is little adoption signal or production hardening, so verify the parent monorepo's CI and composer constraints before relying on it.
Weaver
How can I help you explore Laravel packages today?