Socialite Providers
The aim of this guide is to walk you through setting up a fresh Laravel project with Jetstream, Socialstream and Socialite Providers.
If you're unfamiliar with Laravel Socialite, Jetstream or Socialite Providers, we encourage you to read through their documentation before continuing with this guide.
Before we begin, this guide assumes that you have already setup a fresh Laravel project with Socialstream. If this is not the case, check out the Installation instructions for Socialstream.
Installation
To install a socialite provider, you may do so via composer. For example, to add the Apple provider, you may execute the following command in your terminal:
Setup
Icons
First, we need to create an SVG icon or custom button component for the provider within your desired stack. You will then need to update the published components for your stack to cater for this provider:
Livewire
Icon location: resources/views/components/socialstream-icons/
resources/views/components/socialstream.blade.php
resources/views/components/connected-account.blade.php
Inertia
Icon location: resources/js/Components/SocialstreamIcons/
resources/js/Components/Socialstream.vue
resources/js/Components/ConnectedAccount.vue
Config
Socialstream Providers
Inside your applications socialstream.php
config file, you will want to add the string representation of the SocialiteProvider you are adding support for. For example, if you are adding Sign in With Apple support, you would add the string 'apple'
to the providers
array in config/socialstream.php
Service Provider
Laravel 11+
In bootstrap/providers.php
.
In Laravel 10 or Below
In config\app.php
.
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.
Database Changes โ token
token
Some providers will not return a token in the callback response. As such, you will need to modify the connected_accounts
table migration to make the token
field nullable:
Last updated