8000 Correct default firewall name on Security docs by sdknjg8zxq · Pull Request #7928 · symfony/symfony-docs · GitHub
[go: up one dir, main page]
Skip to content

Correct default firewall name on Security docs #7928

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.

Sign up for GitHub

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

Closed
wants to merge 3 commits into from
Closed

Correct default firewall name on Security docs #7928

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2581138
Change firewall name from "default" to "main"
sdknjg8zxq May 21, 2017
3b06b47
Replace ";" with "." on lists items for consistency
sdknjg8zxq May 20, 2017
88390cb
Don't replace ";" with "." on lists items
sdknjg8zxq May 21, 2017
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
Don't replace ";" with "." on lists items
  • Loading branch information
@sdknjg8zxq
sdknjg8zxq committed May 21, 2017
commit 88390cbf7c6c6ae04f46b0079ea09cefa15c112f
10 changes: 5 additions & 5 deletions security.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,9 +14,9 @@ is both flexible and (hopefully) fun to work with.
Since there's a lot to talk about, this article is organized into a few big
sections:

#. Initial ``security.yml`` setup (*authentication*).
#. Initial ``security.yml`` setup (*authentication*);

#. Denying access to your app (*authorization*).
#. Denying access to your app (*authorization*);

#. Fetching the current User object.

Expand Down Expand Up @@ -611,10 +611,10 @@ basic auth and loads users right from the ``security.yml`` file.
Your next steps depend on your setup:

* Configure a different way for your users to login, like a :ref:`login form <security-form-login>`
or :doc:`something completely custom </security/custom_authentication_provider>`.
or :doc:`something completely custom </security/custom_authentication_provider>`;

* Load users from a different source, like the :doc:`database </security/entity_provider>`
or :doc:`some other source </security/custom_provider>`.
or :doc:`some other source </security/custom_provider>`;

* Learn how to deny access, load the User object and deal with roles in the
:ref:`Authorization <security-authorization>` section.
Expand Down Expand Up @@ -684,7 +684,7 @@ There are **two** ways to deny access to something:

#. :ref:`access_control in security.yml <security-authorization-access-control>`
allows you to protect URL patterns (e.g. ``/admin/*``). This is easy,
but less flexible.
but less flexible;

#. :ref:`in your code via the security.authorization_checker service <security-securing-controller>`.

Expand Down
0