Movatterモバイル変換


[0]ホーム

URL:


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

Sign up
Appearance settings

Commitcd5b7c9

Browse files
wouterjweaverryan
authored andcommitted
Removed repeating text
1 parent7e9233c commitcd5b7c9

File tree

1 file changed

+5
-8
lines changed

1 file changed

+5
-8
lines changed

‎book/security.rst

Lines changed: 5 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -686,14 +686,11 @@ see :doc:`/cookbook/security/form_login`.
686686
Authorization
687687
-------------
688688

689-
The first step in security is always authentication: the process of verifying
690-
who the user is. With Symfony, authentication can be done in any way - via
691-
a form login, basic HTTP Authentication, or even via Facebook.
692-
693-
Once the user has been authenticated, authorization begins. Authorization
694-
provides a standard and powerful way to decide if a user can access any resource
695-
(a URL, a model object, a method call, ...). This works by assigning specific
696-
roles to each user, and then requiring different roles for different resources.
689+
The first step in security is always authentication. Once the user has been
690+
authenticated, authorization begins. Authorization provides a standard and
691+
powerful way to decide if a user can access any resource (a URL, a model
692+
object, a method call, ...). This works by assigning specific roles to each
693+
user, and then requiring different roles for different resources.
697694

698695
The process of authorization has two different sides:
699696

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp