From 92ec62ef1ec9796c9444ff91b5afcd44719287f2 Mon Sep 17 00:00:00 2001 From: Fabien Potencier Date: Thu, 26 Apr 2012 22:54:07 +0200 Subject: [PATCH] [SecurityBundle] added CHANGELOG --- CHANGELOG-2.1.md | 74 ------------------ .../Bundle/SecurityBundle/CHANGELOG.md | 77 +++++++++++++++++++ 2 files changed, 77 insertions(+), 74 deletions(-) create mode 100644 src/Symfony/Bundle/SecurityBundle/CHANGELOG.md diff --git a/CHANGELOG-2.1.md b/CHANGELOG-2.1.md index c122b78de8..a8ce1c1bbd 100644 --- a/CHANGELOG-2.1.md +++ b/CHANGELOG-2.1.md @@ -57,80 +57,6 @@ To get the diff between two versions, go to https://github.com/symfony/symfony/c * This bundle has been moved to its own repository (https://github.com/symfony/MonologBundle) -### SecurityBundle - - * [BC BREAK] The custom factories for the firewall configuration are now - registered during the build method of bundles instead of being registered - by the end-user (you need to remove the 'factories' keys in your security - configuration). - - * [BC BREAK] The Firewall listener is now registered after the Router one. This - means that specific Firewall URLs (like /login_check and /logout must now - have proper route defined in your routing configuration) - - * [BC BREAK] refactored the user provider configuration. The configuration - changed for the chain provider and the memory provider: - - Before: - - ``` yaml - security: - providers: - my_chain_provider: - providers: [my_memory_provider, my_doctrine_provider] - my_memory_provider: - users: - toto: { password: foobar, roles: [ROLE_USER] } - foo: { password: bar, roles: [ROLE_USER, ROLE_ADMIN] } - ``` - - After: - - ``` yaml - security: - providers: - my_chain_provider: - chain: - providers: [my_memory_provider, my_doctrine_provider] - my_memory_provider: - memory: - users: - toto: { password: foobar, roles: [ROLE_USER] } - foo: { password: bar, roles: [ROLE_USER, ROLE_ADMIN] } - ``` - - * [BC BREAK] Method `equals` was removed from `UserInterface` to its own new - `EquatableInterface`. The user class can now implement this interface to override - the default implementation of users equality test. - - * added a validator for the user password - * added 'erase_credentials' as a configuration key (true by default) - * added new events: `security.authentication.success` and `security.authentication.failure` - fired on authentication success/failure, regardless of authentication method, - events are defined in new event class: `Symfony\Component\Security\Core\AuthenticationEvents`. - - * Added optional CSRF protection to LogoutListener: - - ``` yaml - security: - firewalls: - default: - logout: - path: /logout_path - target: / - csrf_parameter: _csrf_token # Optional (defaults to "_csrf_token") - csrf_provider: form.csrf_provider # Required to enable protection - intention: logout # Optional (defaults to "logout") - ``` - - If the LogoutListener has CSRF protection enabled but cannot validate a token, - then a LogoutException will be thrown. - - * Added `logout_url` templating helper and Twig extension, which may be used to - generate logout URL's within templates. The security firewall's config key - must be specified. If a firewall's logout listener has CSRF protection - enabled, a token will be automatically added to the generated URL. - ### SwiftmailerBundle * This bundle has been moved to its own repository (https://github.com/symfony/SwiftmailerBundle) diff --git a/src/Symfony/Bundle/SecurityBundle/CHANGELOG.md b/src/Symfony/Bundle/SecurityBundle/CHANGELOG.md new file mode 100644 index 0000000000..39926aeb2b --- /dev/null +++ b/src/Symfony/Bundle/SecurityBundle/CHANGELOG.md @@ -0,0 +1,77 @@ +CHANGELOG +========= + +2.1.0 +----- + + * [BC BREAK] The custom factories for the firewall configuration are now + registered during the build method of bundles instead of being registered + by the end-user (you need to remove the 'factories' keys in your security + configuration). + + * [BC BREAK] The Firewall listener is now registered after the Router one. This + means that specific Firewall URLs (like /login_check and /logout must now + have proper route defined in your routing configuration) + + * [BC BREAK] refactored the user provider configuration. The configuration + changed for the chain provider and the memory provider: + + Before: + + ``` yaml + security: + providers: + my_chain_provider: + providers: [my_memory_provider, my_doctrine_provider] + my_memory_provider: + users: + toto: { password: foobar, roles: [ROLE_USER] } + foo: { password: bar, roles: [ROLE_USER, ROLE_ADMIN] } + ``` + + After: + + ``` yaml + security: + providers: + my_chain_provider: + chain: + providers: [my_memory_provider, my_doctrine_provider] + my_memory_provider: + memory: + users: + toto: { password: foobar, roles: [ROLE_USER] } + foo: { password: bar, roles: [ROLE_USER, ROLE_ADMIN] } + ``` + + * [BC BREAK] Method `equals` was removed from `UserInterface` to its own new + `EquatableInterface`. The user class can now implement this interface to override + the default implementation of users equality test. + + * added a validator for the user password + * added 'erase_credentials' as a configuration key (true by default) + * added new events: `security.authentication.success` and `security.authentication.failure` + fired on authentication success/failure, regardless of authentication method, + events are defined in new event class: `Symfony\Component\Security\Core\AuthenticationEvents`. + + * Added optional CSRF protection to LogoutListener: + + ``` yaml + security: + firewalls: + default: + logout: + path: /logout_path + target: / + csrf_parameter: _csrf_token # Optional (defaults to "_csrf_token") + csrf_provider: form.csrf_provider # Required to enable protection + intention: logout # Optional (defaults to "logout") + ``` + + If the LogoutListener has CSRF protection enabled but cannot validate a token, + then a LogoutException will be thrown. + + * Added `logout_url` templating helper and Twig extension, which may be used to + generate logout URL's within templates. The security firewall's config key + must be specified. If a firewall's logout listener has CSRF protection + enabled, a token will be automatically added to the generated URL.