Socialite Providers

WARNING

This provider is deprecated. Please see the GitHub Repo (opens new window) for more information

Maintained By GitHub icon atymic
GitHub icon Github Repo
|
Edit

# TeamService

composer require socialiteproviders/microsoft-teamservice

# Installation & Basic Usage

Please see the Base Installation Guide (opens new window), then follow the provider specific instructions below.

# Add configuration to config/services.php

'teamservice' => [    
  'client_id' => env('TEAMSERVICE_CLIENT_ID'),  
  'client_secret' => env('TEAMSERVICE_CLIENT_SECRET'),  
  'redirect' => env('TEAMSERVICE_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('teamservice', \SocialiteProviders\TeamService\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 (opens new window) for detailed instructions.

protected $listen = [
    \SocialiteProviders\Manager\SocialiteWasCalled::class => [
        // ... other providers
        \SocialiteProviders\TeamService\TeamServiceExtendSocialite::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('teamservice')->redirect();

← Jira →