Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

37Signals Laravel Package

socialiteproviders/37signals

Socialite provider for 37signals that adds OAuth authentication to Laravel apps via the Socialite Providers manager. Install it, configure your 37signals credentials, and let users sign in with their 37signals account.

View on GitHub
Deep Wiki
Context7

37signals is an OAuth 1.0a provider for Laravel Socialite, letting your app authenticate users against 37signals services such as Basecamp, Highrise, and Campfire. Since Socialite only ships OAuth 2 support, this package handles the OAuth 1.0a request-token and token-exchange flow for you.

  • Drop-in Socialite::driver('37signals') integration
  • OAuth 1.0a request-token and access-token handling
  • Works with multiple 37signals products
  • Simple event-listener setup in EventServiceProvider
  • Installed via Composer: composer require socialiteproviders/37signals
Frequently asked questions about 37Signals
How do I install the 37signals Socialite provider in Laravel?
Install the package with Composer using socialiteproviders/37signals, then register its SocialiteWasCalled listener according to the SocialiteProviders manager documentation. Add your 37signals client ID, client secret, and callback URL to config/services.php. Because this repository is a subtree split, confirm the exact listener class and setup steps in the package README before deploying.
What configuration does the 37signals Socialite driver need?
The driver uses standard Socialite configuration for a 37signals OAuth app: client ID, client secret, and callback URL. Place these under a 37signals entry in config/services.php and load them from environment variables. The callback URL must exactly match the redirect URI registered in your 37signals application.
Which Laravel versions does socialiteproviders/37signals support?
The supplied overview and release note do not list supported Laravel versions or constraints. Review the package composer.json and CI test matrix before installing or upgrading. The 4.1.0 release is described as adding PHP 8 support, but Laravel compatibility was not supplied in the assessment.
Does socialiteproviders/37signals support PHP 8?
The 4.1.0 release adds PHP 8 support, which improves compatibility with modern Laravel and PHP applications. The assessment notes that the sparse release note does not confirm whether PHP 7 support was dropped or whether behavior changed. Verify the exact PHP 8.x versions, transitive dependencies, and CI coverage in the repository.
How do I authenticate a user with Socialite using the 37signals driver?
After configuration and listener registration, call Socialite::driver('37signals')->redirect() to send users to 37signals. Handle the callback route with Socialite::driver('37signals')->user() and persist the returned user data. Confirm required scopes and available user fields against the 37signals API documentation.
Is socialiteproviders/37signals a standalone package or part of SocialiteProviders?
It is a Composer package that is a subtree split of the SocialiteProviders/37Signals Provider from the SocialiteProviders/Providers repository. You install it through Composer as socialiteproviders/37signals rather than copying provider code. Issues and changes should be tracked upstream in the main SocialiteProviders project.
How can I test 37signals OAuth in Laravel without hitting the real API?
Mock or fake the Socialite driver in feature tests instead of calling the real 37signals OAuth service. Assert redirect generation, callback handling, state validation, and failure paths with controlled responses. Keep real client secrets out of CI and use dedicated test credentials only for staging smoke tests.
What are the production concerns for using this 37signals provider?
Pin the package version and verify Composer dependency resolution, PHP 8 deprecation warnings, and Laravel compatibility before release. Run the full application test suite and Laravel-specific smoke tests in staging. Keep the previous lockfile available for rollback and monitor upstream issues after deployment.
What alternatives exist to socialiteproviders/37signals for 37signals OAuth in Laravel?
You can use Laravel Socialite's custom driver support to implement a 37signals OAuth flow yourself, or call the 37signals API directly. The SocialiteProviders ecosystem includes many providers and a shared manager package. Compare upstream SocialiteProviders/Providers activity and test coverage if you need a long-term maintained integration.
Is socialiteproviders/37signals actively maintained and safe to use?
The assessment rates technical risk as moderate until package metadata and the test matrix are verified. Because release notes are sparse, monitor the upstream SocialiteProviders repository for issues, releases, and maintenance activity. Use pinned versions, CI coverage, and a rollback plan to reduce abandonment or compatibility risk.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
skyraptor/chatter
edlugz/sasapay
abbasudo/artisan-route
mirvan/ippanel
ignibyte/aic-framework
glavweb/data-schema-bundle
glavweb/datagrid-bundle
tacticmedia/scim-server
uni-method/frame
neika-ai/sdk
adachsoft/php-code-style
pharaonic/laravel-notification-dependencies
beautinow/translug
dev-brainiac/bot-cloaked
octoberrain/html
octoberrain/extension
octoberrain/exception
octoberrain/contracts
adachsoft/api-version-bundle
cgv/localized-resource