socialiteproviders/37signals

[READ ONLY] Subtree split of the SocialiteProviders/37Signals Provider (see SocialiteProviders/Providers)

ThirtySevenSignals

composer require socialiteproviders/37signals

Installation & Basic Usage

Please see the Base Installation Guide, then follow the provider specific instructions below.

Add configuration to config/services.php

'37signals' => [    
  'client_id' => env('THIRTYSEVENSIGNALS_CLIENT_ID'),  
  'client_secret' => env('THIRTYSEVENSIGNALS_CLIENT_SECRET'),  
  'redirect' => env('THIRTYSEVENSIGNALS_REDIRECT_URI') 
],

Add provider event listener

Laravel 11+

In Laravel 11, the default EventServiceProvider provider was removed. Instead, add the listener using the listen method on the Event facade, in your AppServiceProvider boot method.

• Note: You do not need to add anything for the built-in socialite providers unless you override them with your own providers.

Event::listen(function (\SocialiteProviders\Manager\SocialiteWasCalled $event) {
    $event->extendSocialite('37signals', \SocialiteProviders\ThirtySevenSignals\Provider::class);
});

Laravel 10 or below

Configure the package's listener to listen for `SocialiteWasCalled` events.

Add the event to your listen[] array in app/Providers/EventServiceProvider. See the Base Installation Guide for detailed instructions.

protected $listen = [
    \SocialiteProviders\Manager\SocialiteWasCalled::class => [
        // ... other providers
        \SocialiteProviders\ThirtySevenSignals\ThirtySevenSignalsExtendSocialite::class.'@handle',
    ],
];

Usage

You should now be able to use the provider like you would regularly use Socialite (assuming you have the facade installed):

return Socialite::driver('37signals')->redirect();