Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Updated security/* articles to Symfony 4 #8735

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Nov 27, 2017
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Fixed the last references to security.yml
  • Loading branch information
javiereguiluz committed Nov 24, 2017
commit c40a9d9201e7c73693ffab88077821c91e2a9748
2 changes: 1 addition & 1 deletion 2 security/entity_provider.rst
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ Introduction
Loading users via a Doctrine entity has 2 basic steps:

#. :ref:`Create your User entity <security-crete-user-entity>`
#. :ref:`Configure security.yml to load from your entity <security-config-entity-provider>`
#. :ref:`Configure security.yaml to load from your entity <security-config-entity-provider>`

Afterwards, you can learn more about :ref:`forbidding inactive users <security-advanced-user-interface>`,
:ref:`using a custom query <authenticating-someone-with-a-custom-entity-provider>`
Expand Down
2 changes: 1 addition & 1 deletion 2 security/form_login_setup.rst
Original file line number Diff line number Diff line change
Expand Up @@ -231,7 +231,7 @@ Finally, create the template:
The form can look like anything, but it usually follows some conventions:

* The ``<form>`` element sends a ``POST`` request to the ``login`` route, since
that's what you configured under the ``form_login`` key in ``security.yml``;
that's what you configured under the ``form_login`` key in ``security.yaml``;
* The username field has the name ``_username`` and the password field has the
name ``_password``.

Expand Down
Morty Proxy This is a proxified and sanitized view of the page, visit original site.