#FOSUserBundle

[freecodetutorial]

implementation of FosUserBundle in Symfony 3.4 a full tutorial here : https://freecodetutorial.com/implementation-fosuserbundle-symfony-3-2/

[alvinbunk]

Symfony LDAP Component AD Authentication

Symfony LDAP Component AD Authentication

Introduction

I previously wrote a very popular article called Symfony AD Integration which uses FOSUserBundle and FR3DLdapBundle, and I wanted to provide a simpler method that uses the Symfony LDAP Component. The main difference with this installation is that it simply authenticates against the server, no user information is stored or managed. If your application needs some type of…

[hacklo5]

Surcharger les routes du FOSUserBundle

Surcharger les routes du FOSUserBundle

Il est évidemment possible de surcharger les routes par défaut du FOSUserBundle dans votre app/config/routing.yml, en re-déclarant celles-ci après l’import du XML des routes du FOSUserBundle.

fos_user_register: resource: "@FOSUserBundle/Resources/config/routing/registration.xml" prefix: /register # ... fos_user_registration_register: path: /account/register defaults: {…

[novidades-symfony]

FOSUserBundle: A entropia dos tokens gerados é perdida

Versões afetadas

Todas as versões 1.0.x, 1.1.x, 1.2.x e 1.3.x do FOSUserBundle são afetadas por esse problema de segurança. A versão de desenvolvimento 2.0.x não é afetada.

O problema foi resolvido no FOSUserBundle 1.3.5. Note que não há soluções fornecidas para as versões 1.0, 1.1 e 1.2 do FOSUserBundle, pois elas não são mais mantidas.

Descrição

Devido ao uso do base_convert, que perde precisão com números grandes, a entropia de tokens gerados pelo FOSUserBundle para o e-mail de confirmação e de redefinição de senha é perdida. Isso torna esses tokens muito menos aleatórios do que se espera, e, assim, não criptograficamente seguros.

Resolução

A lógica de geração de token utilizada na branch 2.0.x com base na codificação base64 foi portada. Isso muda a gama de caracteres usados ​​no token. Qualquer placeholder de rota previsto para coincidir com um token gerado pelo FOSUserBundle deve ser atualizado para permitir traços, os quais não são permitidos pelo \w em expressões regulares. Um requirement \w+ deve tornar-se [\w\-]+.

Créditos

Agradecimentos para Andreas Forsblom por relatar esse problema de segurança e Jonathan McLean por contribuir com a implementação que foi portada.

Tradução de: FOSUserBundle: Entropy of generated tokens is lost por Christophe Coevoet

[ikonenn-blog]

FOSOAuthServerBundle et FOSUserBundle - OAuth2

FOSOAuthServerBundle et FOSUserBundle – OAuth2

FOSOAuthServerBundle – implémentation de l’OAuth2 entre deux apps Objectif

Sur un projet il m’a fallu implémenter l’OAuth2 entre deux plates-formes à savoir une application Symfony2 (avec FOSOAuthServerBundle) et un site WordPress. L’objectif étant qu’un visiteur sur le site WordPress (déjà utilisateur ou non) puisse se logguer à son administration avec le mécanisme d’authentification présent sur…

[riceandbytes-blog-blog]

FOSUserBundle Emails

The FOSUserBundle has built-in support for sending emails in two different instances.

Registration Confirmation

The first is when a new user registers and the bundle is configured to require email confirmation before the user registration is complete. The email that is sent to the new user contains a link that, when visited, will verify the registration and enable the user account.

Requiring email confirmation for a new account is turned off by default. To enable it, update your configuration as follows:

# app/config/config.yml fos_user: # ... registration: confirmation: enabled: true

Password Reset

An email is also sent when a user has requested a password reset. The FOSUserBundle provides password reset functionality in a two-step process. First the user must request a password reset. After the request has been made, an email is sent containing a link to visit. Upon visiting the link, the user will be identified by the token contained in the url. When the user visits the link and the token is confirmed, the user will be presented with a form to enter in a new password.

Default Mailer Implementations

The bundle comes with three mailer implementations. They are listed below by service id:

fos_user.mailer.default is the default implementation, and uses Swiftmailer to send emails.

fos_user.mailer.twig_swift uses Swiftmailer to send emails and Twig blocks to render the message.

fos_user.mailer.noop is a mailer implementation which performs no operation, so no emails are sent.

Note:

The fos_user.mailer.noop mailer service should be used in the case where you do not want the bundle to send emails and you do not want to include the SwiftmailerBundle in your app. If you leave the default implementation configured as the mailer and do not have the SwiftmailerBundle registered, you will receive an exception because of a missing dependency.

Configuring the Sender Email Address

The FOSUserBundle default mailer allows you to configure the sender email address of the emails sent out by the bundle. You can configure the address globally or on a per email basis.

To configure the sender email address for all emails sent out by the bundle, simply update your fos_user config as follows:

# app/config/config.yml fos_user: #... from_email: address: noreply@acmedemo.com sender_name: Acme Demo App

The bundle also provides the flexibility of allowing you to configure the sender email address for the emails individually.

To configure the sender email address for the user registration confirmation email update your fos_user config as follows:

# app/config/config.yml fos_user: #... registration: confirmation: from_email: address: registration@acmedemo.com sender_name: Acme Demo Registration

You can similarly update the fos_user config to change the sender email address for the password reset request email:

# app/config/config.yml fos_user: #... resetting: email: from_email: address: resetting@acmedemo.com sender_name: Acme Demo Resetting

Sending HTML mails

The default mailer only supports sending plain text messages. If you want to send multipart messages, the easiest solution is to use the TwigSwiftMailer implementation instead. It expects your twig template to define 3 blocks:

subject containing the email subject

body_text rendering the plain text version of the message

body_html rendering the html mail

Here is how you can use it:

# app/config/config.yml fos_user: # ... service: mailer: fos_user.mailer.twig_swift resetting: email: template: AcmeDemoBundle:User:resetting.email.twig

{# src/Acme/DemoBundle/Resources/views/User/resetting.email.twig #} {% block subject %}Resetting your password{% endblock %} {% block body_text %} {% autoescape false %} Hello {{ user.username }} ! You can reset your email by accessing {{ confirmationUrl }} Greetings, the Acme team {% endautoescape %} {% endblock %} {% block body_html %} {# You can of course render the html directly here. Including a template as done here allows keeping things DRY by using the template inheritance in it #} {% include 'AcmeDemoBundle:User:resetting_email.html.twig' %} {% endblock %}

Note:

The HTML part is set in the message only when the body_html block is not empty.

Using A Custom Mailer

The default mailer service used by FOSUserBundle relies on the Swiftmailer library to send mail. If you would like to use a different library to send emails, want to send HTML emails or simply change the content of the email you may do so by defining your own service.

First you must create a new class which implements FOS\UserBundle\Mailer\MailerInterface which is listed below.

<?php namespace FOS\UserBundle\Mailer; use FOS\UserBundle\Model\UserInterface; /** * @author Thibault Duplessis <thibault.duplessis@gmail.com> */ interface MailerInterface { /** * Send an email to a user to confirm the account creation * * @param UserInterface $user */ function sendConfirmationEmailMessage(UserInterface $user); /** * Send an email to a user to confirm the password reset * * @param UserInterface $user */ function sendResettingEmailMessage(UserInterface $user); }

After you have implemented your custom mailer class and defined it as a service, you must update your bundle configuration so that FOSUserBundle will use it. Simply set the mailer configuration parameter under the service section. An example is listed below.

In YAML:

# app/config/config.yml fos_user: # ... service: mailer: acme.mailer

To see an example of a working implementation of the MailerInterface see the ZetaMailer class of the ZetaWebmailBundle. This implementation uses the Zeta Components Mail to send emails instead of Swiftmailer.