Life Science Login

composer require socialiteproviders/lifesciencelogin

Installation & Basic Usage

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

Add configuration to config/services.php

'lifesciencelogin' => [    
  'client_id' => env('LSLOGIN_CLIENT_ID'),  
  'client_secret' => env('LSLOGIN_CLIENT_SECRET'),  
  'redirect' => env('LSLOGIN_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('lifesciencelogin', \SocialiteProviders\LifeScienceLogin\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\LifeScienceLogin\LifeScienceLoginExtendSocialite::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('lifesciencelogin')->redirect();

Returned User Fields

• id
• name
• given_name
• family_name
• email

Funding

The development of this provider was supported by the German Research Foundation (DFG) within the project “Establishment of the National Research Data Infrastructure (NFDI)” in the consortium NFDI4Biodiversity (project number 442032008).