dayspring-tech/login-bundle

Form login user authentication for Symfony2, with forgot/reset password, change password.

5.2.0 2023-07-11 03:54 UTC

Requires

• php: >=7.4
• dayspring-tech/propel-bundle: ^1.8.6
• doctrine/annotations: ^1.12.1
• egulias/email-validator: ^2.1.25|^3.0|^4.0
• sensio/framework-extra-bundle: ^5.0.1
• symfony/asset: ^4.0|^5.0
• symfony/console: ^4.0|^5.0
• symfony/expression-language: ^4.0|^5.0
• symfony/form: ^4.0|^5.0
• symfony/framework-bundle: ^4.4.23|^5.0
• symfony/mailer: ^4.0|^5.0
• symfony/monolog-bundle: ^3.6.0
• symfony/routing: ^4.0|^5.0
• symfony/security-bundle: ^4.0|^5.0
• symfony/twig-bundle: ^4.4.19|^5.0
• symfony/validator: ^4.0|^5.0
• symfony/yaml: ^4.0|^5.0

Requires (Dev)

• phpunit/phpunit: ^8.5.23|^9.0
• symfony/browser-kit: ^4.0|^5.0
• symfony/css-selector: ^4.0|^5.0
• symfony/phpunit-bridge: ^5.0|^6.0

Conflicts

• symfony/password-hasher: >=6.0

MIT

• Jeffrey Wong
• Matt Crawford
• Stanley Situ

• login
• user authentication
• change password
• reset password
• forgot password

README

This bundle provides basic username/password authentication, forgot/reset password, and change password.

Minimally, your security.yml should contain the following:

security:
    providers:
        dayspring:
            id: dayspring_login.user_provider
    password_hashers:
        Dayspring\LoginBundle\Model\User:
            algorithm: bcrypt
            cost: 12
    firewalls:
        dev:
            pattern: ^/(_(profiler|wdt)|css|images|js)/
            security: false
        login:
            pattern:  ^/login$
            security: false
        secured_area:
            pattern:    ^/
            user_checker: dayspring_login.user_checker
            form_login:
                check_path: _login_check
                login_path: _login
                default_target_path: /_demo/secure
                provider: dayspring
                success_handler: dayspring_login.success_handler
            logout:
                path:   _logout
                target: /
            anonymous: ~

User Profiles

If your application requires additional information to be stored with the user, the recommended strategy is to create a UserProfile model using Propel's inheritance features. http://propelorm.org/Propel/documentation/09-inheritance.html#class-table-inheritance

Example:

<table name="user_profiles" phpName="UserProfile" idMethod="native">
  <behavior name="concrete_inheritance">
    <parameter name="extends" value="users" />
  </behavior>
  <column name="first_name" type="VARCHAR" size="100"/>
  <column name="last_name" type="VARCHAR" size="100"/>
</table>