forci/login-bundle

A Symfony ~3.0 Bundle that eases logging users to your Symfony application.

Login Bundle

A Symfony ~3.0|~4.0 Bundle that eases logging users to your Symfony application., _(*1)

Configuration Sample, _(*2)

forci_login:
    managers:
        frontend:
            firewall_name: frontend_area # Your firewall name
            hwi_oauth: # HWIOAuthBundle integration - for use directly with OAuth Access Tokens
                enabled: true
                token_class: Forci\Bundle\LoginBundle\HWIOAuth\OAuthToken # You may change the token class to this
                # Or to your own class that extends the Bundle's token class. Using the above example 
                # In combination with the below setting will force the Token to return true to isAuthenticated calls
                # This resolves HWIOAuthBundle's issues with serialization and/or your users not having any roles by default
                # Which mostly leads to making HTTP requests to the OAuth APIs on E V E R Y page load.
                # PS You may also use that class, or your own implementation of this idea and a custom 
                # \HWI\Bundle\OAuthBundle\Security\Core\Authentication\Provider\OAuthProvider to prevent that
                # In the case of a normal web-redirect login flow with the bundle
                always_authenticated: true
                user_provider: app.auth.user_provider

<?php 
/** @var \Symfony\Component\DependencyInjection\ContainerInterface */
$container;
/** @var \Forci\Bundle\LoginBundle\Helper\LoginHelper $manager */
$manager = $container->get('forci_login.helper.frontend'); // where frontend is your config key
$manager->logInUser($user);
$manager->rememberUser($user, $response);
$manager->logInHWIOAuthAccessToken($accessToken, $state, $resourceOwner);
$manager->rememberHWIOAuthAccessToken($accessToken, $state, $resourceOwner, $response);

<?php
/** @var \Symfony\Component\DependencyInjection\ContainerInterface */
$container;
$manager = $container->get('forci_login.helper.silent');
// $user is your User object
// some_area_key is your firewall key
// some_area_context is your security context config for your firewall
// Sample config down below, just for example purposes
$manager->loginSilent($user, 'some_area_key', 'some_area_context');

security:
    firewalls:
        some_area_key:
            pattern: ^/some/path
            context: some_area_context

TODOs

• Possibly extend UsernamePasswordToken and make it configurable, again with the option to always be considered authenticated?, _(*3)

• Have a good look at those services from Symfony Security and consider implementing calls to those as otherwise redirect target path will not be correctly cleared upon success?, _(*4)

, _(*5)

, _(*6)

, _(*7)

, _(*8)

• Have a look at PreAuthenticatedToken ?g