README

Directly inspired from FOSUserBundle, and migration of c975L/UserFilesBundle, UserBundle does the following:

Ensure respect of GDPR rules such as giving agreement to store data, exporting data,
Stores users in database (using doctrine),
Provides multiples types of entities for User (see below),
Allows extending those entities to add your own fields,
Allows users to manage their profile and data,
Validates data such as Siret, VAT number,
Displays a "challenge" for sign up (no Captcha, etc.),
Allows the possibility to disable sign up (for registering only one or more users and then no more),
Provides forms for Sign in, Sign up, Modify profile, Change password and Reset password,
Provides public profile (you can disabled it in config),
Allows extending those forms,
Sends email about sign up and password reset to the user via c975LEmailBundle as c975LEmailBundle provides the possibility to save emails in a database, there is an option to NOT do so via this Bundle,
Integrates with c975LToolbarBundle,
Allows to connect with social networks via HWIOAuthBundle,
Provides a sql script to migrate from FOSUserBundle,
Allows to display Gravatar's image linked to the email address,
Allows to display Social network's image linked to the account,
Provides a divData to allows access user's data from javascript,
Allows easy overridding of templates or parts of them to minimize the number of the overriden files to the essential,
Allows to define a number of attempts for sign in and then add a delay before being able to sign in again,
Resetting password form will NOT send email for inexisting accounts while displaying so, this un-allows checking for registered emails,
Allows user to removes its allowing to use its data while maintaining its account, in this case the account will be marked as NOT enabled,
Sends email when user changes (or resets) passsword to allow contact website if he/she has not initiated this action,
integrates an API to authenticate/create/display/modify/delete users in json format,

Bundle installation

Step 1: Download the Bundle

v3.x works with Symfony 4.x. Use v2.x for Symfony 3.x Use Composer to install the library

    composer require c975l/user-bundle

Step 2: Configure the Bundle

Check dependencies for their configuration:

And finally in /config/packages/security.yml

security:
    encoders:
        #The entity you want to use
        c975L\UserBundle\Entity\User: auto
    role_hierarchy:
        ROLE_MODERATOR: 'ROLE_USER'
        ROLE_ADMIN: [ROLE_MODERATOR, ROLE_USER]
        ROLE_SUPER_ADMIN: [ROLE_ADMIN, ROLE_MODERATOR, ROLE_USER]
    providers:
        c975_l_userbundle:
            entity:
                #The entity you want to use
                class: c975L\UserBundle\Entity\User
    firewalls:
        main:
            pattern: ^/
            provider: c975_l_userbundle
            form_login:
                login_path: user_signin
                check_path: user_signin
                default_target_path: user_dashboard
                csrf_token_generator: security.csrf.token_manager
            remember_me:
                secret: '%secret%'
                lifetime: 31536000
                path: /
                secure: true
            anonymous: true
            logout:
                path: user_signout
                handlers: [c975L\UserBundle\Listener\LogoutListener]

Step 3: Create MySql table

Use /Resources/sql/user.sql to create the tables user and user_archives. The DROP TABLE are commented to avoid dropping by mistake. It will also create a stored procedure sp_UserArchive().

Step 4: Enable the Routes

Then, enable the routes by adding them to the /config/routes.yaml file of your project:

c975_l_user:
    resource: "@c975LUserBundle/Controller/"
    type: annotation
    prefix: /
    #Multilingual website use the following
    #prefix: /{_locale}
    #defaults:   { _locale: '%locale%' }
    #requirements:
    #    _locale: en|fr|es

Step 5: install assets to web folder

Install assets by running

php bin/console assets:install --symlink

It will create a link from folder Resources/public/ in your web folder.

Overriding Templates

It is strongly recommended to use the Override Templates from Third-Party Bundles feature to integrate fully with your site.

For this, simply, create the following structure /templates/bundles/c975LUserBundle/ in your app and then duplicate the file layout.html.twig in it, to override the existing Bundle files, then apply your needed changes.

You can also override:

/templates/bundles/c975LUserBundle/fragments/deleteAccountInfo.html.twig that will list the implications, by deleting account, for user, displayed in the delete account page.
/templates/bundles/c975LUserBundle/fragments/dashboardActions.html.twig to add your own actions (or whatever) in the dashboard i.e.
/templates/bundles/c975LUserBundle/fragments/avatar.html.twig to modify the display of avatar (26/03/2018)

You can add a navbar menu via {% include('@c975LUser/fragments/navbarMenu.html.twig') %}. You can override it, if needed, or simply override /templates/bundles/c975LUserBundle/fragments/navbarMenuActions.html.twig to add actions above it.

Routes

The Routes availables are:

user_signup
user_signup_confirm
user_signin
user_config
user_dashboard
user_display
user_export
user_modify
user_change_password
user_reset_password
user_reset_password_confirm
user_signout
user_delete
user_public_profile

Entities

You must choose an entity linked to your needs and specify it in the /config/packages/security.yml. Available entities are the following:

c975L/UserBundle/Entity/UserLight: light user with minimum requirements
c975L/UserBundle/Entity/User: default user
c975L/UserBundle/Entity/UserAddress: default user + address fields
c975L/UserBundle/Entity/UserBusiness: default user + business/association fields
c975L/UserBundle/Entity/UserSocial: default user + social network fields
c975L/UserBundle/Entity/UserFull: default user + address + business + social + multilingual fields

To help you choose, the fields are the following:

LIGHT

id
allow_use
identifier
email
creation
enabled
salt
password
token
password_request
roles

DEFAULT

gender
firstname
lastname
avatar
latest_signin
latest_signout
locale

ADDRESS

address
address2
postal
town
country
phone
fax

BUSINESS

business_type
business_name
business_address
business_address2
business_postal
business_town
business_country
business_siret
business_vat
business_phone
business_fax

SOCIAL

social_network
social_id
social_token
social_picture

You can also create your own Class by extending one of the Abstract classes with the following code:

<?php
//Your Entity file i.e. src/App/Entity/User.php
namespace App\Entity;

use c975L\UserBundle\Entity\UserAbstract;

class User extends UserAbstract
{
    //Add your properties and methods
}

Extending Forms

You can extend UserSignupType and UserProfileType. To extend them, to include new properties or features, simply use the following code:

<?php
//Your own form i.e. src/App/Form/UserProfileType
namespace App\Form;

use c975L\UserBundle\Form\UserProfileType as BaseProfileType;

class UserProfileType extends BaseProfileType
{
    //Builds the form
    public function buildForm(FormBuilderInterface $builder, array $options)
    {
        //You can use the following to disable/enable fields
        $disabled = $options['data']->getAction() == 'modify' ? false : true;

        //Add the fields you need
    }

    public function getParent()
    {
        return 'c975L\UserBundle\Form\UserProfileType';
    }

    public function getBlockPrefix()
    {
        return 'app_user_profile';
    }
}

Then you have to add it as a service in your app/config/services.yml:

services:
    _defaults:
        autowire: true
        autoconfigure: true
        public: true
    App\Form\:
        resource: '../../src/App/Form/*'

And finally, you have to set it in your app/config/config.yml

c975_l_user:
    signupForm: 'App\Form\UserSignupType'
    profileForm: 'App\Form\UserProfileType'

Events

Multiples events are fired to help you fit your needs, they are all defined in Event\UserEvent.php. For example if you need to perform taks before deleting a user, you can create a Listener like this:

<?php

namespace App\Listener;

use c975L\UserBundle\Entity\UserAbstract;
use c975L\UserBundle\Event\UserEvent;
use Symfony\Component\EventDispatcher\EventSubscriberInterface;
use Symfony\Component\Security\Core\User\UserInterface;

class UserDeleteListener implements EventSubscriberInterface
{
    public static function getSubscribedEvents()
    {
        return array(
            UserEvent::USER_DELETE => 'userDelete',
        );
    }

    public function userDelete($event)
    {
        $user = $event->getUser();

        if ($user instanceof UserInterface) {
            //Do your stuff...

            //Use the following is you want to stop propagation of the Event, any following instructions will be stopped
            //$event->stopPropagation();
        }
    }
}

Service

You can inject c975L\UserBundle\Service\UserServiceInterface to access its methods. For example you can retrieve a user with its id, email, socialId, ...

//Within a controller
use c975L\UserBundle\Service\UserServiceInterface;

    public function yourAction(UserServiceInterface $userService)
    {
        //With Id
        $user = $userService->findUserById(USER_ID);

        //With Email
        $user = $userService->findUserByEmail(USER_EMAIL);

        //With Identifier
        $user = $userService->findUserByIdentifier(USER_IDENTIFIER);

        //With SocialId
        $user = $userService->findUserBySocialId(USER_SOCIAL_ID);
    }

Sign in/Sign out link

If you want to insert a link to sign in/sign out, i.e. in the footer, you can do it via this code:

{# Sign in/Sign out #}
<p class="text-center">
    {% include '@c975LUser/fragments/signinSignout.html.twig' %}
</p>

User Div data for javascript use

If you want to insert a div containing the user's data, to be used by javascript, you can do it via the Twig extension:

{# User DivData #}
{{ user_divData() }}

Then you can access it via

$(document).ready(function() {
    var firstname = $('#user').data('firstname');
});

Have a look at it to see the properties covered.

Custom redirect after sign in

If you want to redirect to a specific page you can use Request Parameters with the following code:

//In a Controller file
return $this->redirectToRoute('user_signin', array('_target_path' => 'THE_ABSOLUTE_OR_RELATIVE_URL_TO_REDIRECT_TO'));

User's avatar

You can display the avatar linked to user's account (if enabled in config.yml) by calling the Twig extension where you want to place it:

{{ user_avatar() }}
{# Or with specifying its size, 128 by default #}
{{ user_avatar(64) }}

Twig extension

You can use Twig extensions to format VAT and Siret numbers.

{{ 'YOUR_VAT_NUMBER'|user_vat }}
{{ 'YOUR_SIRET_NUMBER'|user_siret }}

Using HwiOauth (Social network sign in)

On the sign in form you can add links to sign in/sign up with social networks via HWIOAuthBundle. If you want to this feature, simply add in your /config/config_bundles.yaml or using c975L\ConfigBundle and clear the cache, the following:

c975LUser:
    hwiOauth: ['facebook', 'google', 'live']
    social: true

And in your /config/services.yaml, the following:

services:
    c975L\UserBundle\Security\OAuthUserProvider:
        public: true

c975L/UserBundle doesn't implement the connection with social networks but provides a bridge with HWIOAuthBundle. To display buttons on the sign in page and to store users in the DB, you have to configure HWIOAuthBundle by your own. This will mainly consist in setting differents informations in config files. As an example, they are listed below, for Facebook, but other networks will work in the same way:

#routes.yaml
hwi_oauth_redirect:
    resource: "@HWIOAuthBundle/Resources/config/routing/redirect.xml"
    prefix:   /connect
hwi_oauth_connect:
    resource: "@HWIOAuthBundle/Resources/config/routing/connect.xml"
    prefix:   /connect
hwi_oauth_login:
    resource: "@HWIOAuthBundle/Resources/config/routing/login.xml"
    prefix:   /login
facebook_login:
    path: /login/facebook

#parameters.yml
#As a Best Practice, it is preferable to declare your secret parameters in parameters.yml file in place of config.yml.
#Then you can re-use them with "%facebook_app_id%".
parameters:
    facebook_app_id: 'YOUR_FACEBOOK_APP_ID'
    facebook_app_secret: 'YOUR_FACEBOOK_APP_SECRET'

#parameters.yml.dist
parameters:
    facebook_app_id: ~
    facebook_app_secret: ~

You will have to declare the account_connector c975L\UserBundle\Security\OAuthUserProvider

#config.yml
hwi_oauth:
    connect:
        confirmation: true
        account_connector: c975L\UserBundle\Security\OAuthUserProvider
    firewall_names: [main]
    resource_owners:
        facebook:
            type: facebook
            client_id: "%facebook_app_id%"
            client_secret: "%facebook_app_secret%"
            scope: "email"
            options:
                csrf: true
                display: popup

You will have to declare the oauth_user_provider c975L\UserBundle\Security\OAuthUserProvider

#security.yml
security:
    #...
    firewalls:
        main:
            oauth:
                resource_owners:
                    facebook: "/login/facebook"
                login_path: user_signin
                failure_path: user_signin
                use_forward: true
                default_target_path: user_dashboard
                oauth_user_provider:
                    service: c975L\UserBundle\Security\OAuthUserProvider

Social networks images

c975L/UserBundle provides images for some of the social networks, they were linked in your web folder when you have installed the assets (see above). If the network you want to use has not an image yet, you can use the file `Resources/SocialNetwork/signin.svg`` to build one and make a PR to add it to the bundle :-).

You can also override Resources/views/fragments/socialNetworkImage.html.twig with your own pictures set or to change the styles used.

As a "Bonus" if a user has signed up with its email address and then use a social network to signin, it will get its existing user account IF emails addresses are the same, otherwise, it will create another account.

Signing up with another social network, after having already signed up with a different one, will replace the current one by the new one.

Migration from FOSUserBundle

If you want to migrate from FOSUserBundle, you have to do the following:

Remove from composer

composer remove friendsofsymfony/user-bundle

Migrate your database table, by using Resources\sql\MigrateFosUser.sql. It will create a user_migrate table, will modify all the needed fields, will add missing ones, then, when you are ready, you can rename your FOSUSerBundle table to user_fosuserbundle (or whatever you want) and rename the user_migrate one to user. Fields username and groups are kept but not used, so you can delete them if you don't use them.

API Documentation

You can also use the API provided in c975LUserBundle with the following:

You have to use https://github.com/lcobucci/jwt (openssl extension is required).

Then create your RSA keys:

cd <your_root_project_dir>;
mkdir -p config/jwt;
openssl genrsa -out config/jwt/private.pem -aes256 4096;
#If it requires passPhrase then enter one and un-comment and run the following
#openssl rsa -in config/jwt/private.pem -out config/jwt/private2.pem;
#mv config/jwt/private.pem config/jwt/private.pem-back;
#mv config/jwt/private2.pem config/jwt/private.pem;
#rm config/jwt/private.pem-back;
openssl rsa -pubout -in config/jwt/private.pem -out config/jwt/public.pem;

Add those paths to /config/config_bundles.yaml or using c975L\ConfigBundle :

c975LUser:
    privateKey: 'config/jwt/private.pem'
    publicKey: 'config/jwt/public.pem'
    api: true
    apiOnly: true #If you wish to only use API and not the web forms

Define the JSON end point in your security.yaml:

security:
    firewalls:
        main:
            json_login:
                check_path: user_api_authenticate
            anonymous: true
            guard:
                authenticators:
                    - c975L\UserBundle\Security\TokenAuthenticator

Then you can use the different Routes :

Except for user_api_create and user_api_authenticate you need to send the JWT (obtained via user_api_authenticate) in the header Authorization: Bearer <token> (recommended) or in the header X-AUTH-TOKEN: <token> for all the API Routes requests.

`/user/api/create`

methods={"HEAD", "POST"}. To create the user, call the Route, in a POST request, user_api_create with the form-data fields needed by the User entity chosen (see above). Fields email and plainPassword are mandatory any other will be added to the Entity if the Method exists. You also need to add a field apiKey which consists of sha1($email . apiPassword), apiPassword is defined in the user_config Route. It is also recommended to define CORS access.

`/user/api/authenticate`

methods={"HEAD", "POST"}. To authenticate, call the Route user_api_authenticate with the JSON body {"username": "<email>", "password": "<password>"} in a POST request, with the header Content-Type: application/json, you will receive a token. You can fix the expiration time of the JWT by adding "expiration": <delay_inseconds> to the json data sent.

`/user/api/display/{identifier}`

methods={"HEAD", "GET"}, {identifier} -> [0-9a-z]{32}. To display the user, call the Route user_api_display, in a GET request, with the identifier of the user. The user defined in JWT must have sufficients rights, as configured in user_config Route or be the user itself.

`/user/api/list[?page=1&size=50]`

methods={"HEAD", "GET"}. To list the users, call the Route user_api_list in a GET request. You can use the query parameters page (default 1) to define which page and size (default 50) to define the number of records to display. The user defined in JWT must have sufficients rights, as configured in user_config Route.

`/user/api/search/{term}[?page=1&size=50]`

methods={"HEAD", "GET"}, {term} -> [0-9a-zA-Z]+. To search within the users, call the Route user_api_search, in a GET request, with the term searched that will be matched as %term% with the email field of the User entity. You can use the query parameters page (default 1) to define which page and size (default 50) to define the number of records to display. The user defined in JWT must have sufficients rights, as configured in user_config Route.

`/user/api/modify/{identifier}`

methods={"HEAD", "PUT"}, {identifier} -> [0-9a-z]{32}. To modify the user, call the Route user_api_modify in a PUT request, with the identifier of the user and the data fields in the body of the request i.e. {"email": "mail@example.com"} needed by the User entity chosen (see above). The user defined in JWT must have sufficients rights, as configured in user_config Route or be the user itself.

`/user/api/delete/{identifier}`

methods={"HEAD", "DELETE"}, {identifier} -> [0-9a-z]{32}. To delete the user, call the Route user_api_delete in a DELETE request, with the identifier of the user. the user will be archived if you have defined it in the Config parameters. The user defined in JWT must have sufficients rights, as configured in user_config Route or be the user itself.

`/user/api/add-role/{identifier}/{role}`

methods={"HEAD", "PUT"}, {identifier} -> [0-9a-z]{32}, {role} -> [a-zA-Z\_]+. To add a Role to the user, call the Route user_api_add_role in a PUT request, with the identifier of the user and the role you want to assign. The user defined in JWT must have sufficients rights, as configured in user_config Route.

`/user/api/delete-role/{identifier}/{role}`

methods={"HEAD", "PUT"}, {identifier} -> [0-9a-z]{32}, {role} -> [a-zA-Z\_]+. To delete a Role of the user, call the Route user_api_delete_role in a PUT request, with the identifier of the user and the role you want to delete. The user defined in JWT must have sufficients rights, as configured in user_config Route.

`/user/api/modify-roles/{identifier}`

methods={"HEAD", "PUT"}, {identifier} -> [0-9a-z]{32}. To modify the Roles of the user, call the Route user_api_modify_roles in a PUT request, with the identifier of the user and an array of roles in the body of the request i.e. {"roles": ["ROLE_ADMIN", "ROLE_USER"]}. The user defined in JWT must have sufficients rights, as configured in user_config Route.

`/user/api/change-password`

methods={"HEAD", "PUT"}. To change the password of a defined user, call the Route user_api_change_password in a PUT request with the data field plainPassword in the body of the request i.e. {"plainPassword": "BrandNewPass*$1"}. Only the user defined in JWT can change its password.

`/user/api/reset-password` & `/user/api/reset-password-confirm`

methods={"HEAD", "PUT"}. To reset the password of a defined user, call the Route user_api_reset_password in a PUT request with an array with the field email in the body of the request i.e. {"email": "email@example.com"}, you will receive a token and its validity time (2 hours later). Then, to confirm (and change) the password, you have to call the route user_api_reset_password_confirm with /user/api/reset-password-confirm/{token} with the data field plainPassword in the body of the request i.e. {"plainPassword": "BrandNewPass*$1"}.

`/user/api/export`

methods={"HEAD", "GET"}. To export user's data, call the Route user_api_export in a GET request. Only the user defined in JWT can access its data. If you wish to add data you can listen to UserEvent::API_USER_EXPORT and update the user or you can export your own foramtted data by using the following in an EventListener:

use Symfony\Component\EventDispatcher\EventSubscriberInterface;
use Symfony\Component\HttpFoundation\Response;
use Symfony\Component\Security\Core\User\UserInterface;

class UserListener implements EventSubscriberInterface
{
    public static function getSubscribedEvents()
    {
        return array(
            UserEvent::API_USER_EXPORT => 'userApiExport',
        );
    }

    public function userApiExport($event)
    {
        $response = null;
        $user = $event->getUser();
        if ($user instanceof UserInterface) {
            $userFormattedData = array();

            $response = new Response(json_encode($userFormattedData));
            $response->headers->set('Content-Type', 'application/json');
        }

        $event
            ->setResponse($response)
            ->stopPropagation()
        ;
    }
}

If this project help you to reduce time to develop, you can sponsor me via the "Sponsor" button at the top :)

c975l / user-bundle

Maintainers

Details

README

Bundle installation

Step 1: Download the Bundle

Step 2: Configure the Bundle

Step 3: Create MySql table

Step 4: Enable the Routes

Step 5: install assets to web folder

Overriding Templates

Routes

Entities

Extending Forms

Events

Service

Sign in/Sign out link

User Div data for javascript use

Custom redirect after sign in

User's avatar

Twig extension

Using HwiOauth (Social network sign in)

Social networks images

Migration from FOSUserBundle

API Documentation

`/user/api/create`

`/user/api/authenticate`

`/user/api/display/{identifier}`

`/user/api/list[?page=1&size=50]`

`/user/api/search/{term}[?page=1&size=50]`

`/user/api/modify/{identifier}`

`/user/api/delete/{identifier}`

`/user/api/add-role/{identifier}/{role}`

`/user/api/delete-role/{identifier}/{role}`

`/user/api/modify-roles/{identifier}`

`/user/api/change-password`

`/user/api/reset-password` & `/user/api/reset-password-confirm`

`/user/api/export`

c975l / user-bundle

Maintainers

Details

README

Bundle installation

Step 1: Download the Bundle

Step 2: Configure the Bundle

Step 3: Create MySql table

Step 4: Enable the Routes

Step 5: install assets to web folder

Overriding Templates

Routes

Entities

Extending Forms

Events

Service

Sign in/Sign out link

User Div data for javascript use

Custom redirect after sign in

User's avatar

Twig extension

Using HwiOauth (Social network sign in)

Social networks images

Migration from FOSUserBundle

API Documentation

/user/api/create

/user/api/authenticate

/user/api/display/{identifier}

/user/api/list[?page=1&size=50]

/user/api/search/{term}[?page=1&size=50]

/user/api/modify/{identifier}

/user/api/delete/{identifier}

/user/api/add-role/{identifier}/{role}

/user/api/delete-role/{identifier}/{role}

/user/api/modify-roles/{identifier}

/user/api/change-password

/user/api/reset-password & /user/api/reset-password-confirm

/user/api/export

`/user/api/create`

`/user/api/authenticate`

`/user/api/display/{identifier}`

`/user/api/list[?page=1&size=50]`

`/user/api/search/{term}[?page=1&size=50]`

`/user/api/modify/{identifier}`

`/user/api/delete/{identifier}`

`/user/api/add-role/{identifier}/{role}`

`/user/api/delete-role/{identifier}/{role}`

`/user/api/modify-roles/{identifier}`

`/user/api/change-password`

`/user/api/reset-password` & `/user/api/reset-password-confirm`

`/user/api/export`