the csrf_provider change is also done in 2.8 (deprecating the old one). Otherwise, it would not have matched our upgrade policy

and the change should be done in the 2.8 branch actually, to avoid using the deprecated names

We can add something like the following below the configuration block:

..versionadded::2.8    The ``intention`` and ``csrf_token_generator`` options were introduced    in Symfony 2.8. Prior, you had to use the ``csrf_token_id`` and ``csrf_provider``    options.

@Raistlfiren You can make the changes here. We should be able to safely backport the PR to the2.8 branch when merging and then merge things up to themaster branch.

Need a new commit to rebuild this PR on Platform.sh.

The SecurityBundle configuration reference should also be updated:http://symfony.com/doc/2.8/reference/configuration/security.html

I was a little bit confused while upgrading to Symfony 3.0.
This documentation should be updated for 2.8, 3.0 and 3.1:
http://symfony.com/doc/master/cookbook/security/csrf_in_login_form.html

We're getting more and more reports from users suffering this issue while upgrading to 3.0. Let me know if we can help you in any way to get this merged soon. Thanks!

Thank you@Raistlfiren for starting this. I have taken your changes and finished them in#6152. That's why I close here. However, you will still get the full credit for your contribution as I kept all your commits.