Skip to content

Commit 903893c

Browse files
committed
minor #17438 [Security] Merging "list" into text (ThomasLandauer)
This PR was merged into the 5.4 branch. Discussion ---------- [Security] Merging "list" into text Reason: "a few guidelines" sounded odd, cause the first was no guideline (but a rule), and the second was still no guideline (but more details to first). Commits ------- 97c38f3 Merging "list" into text
2 parents 1f999bf + 97c38f3 commit 903893c

File tree

1 file changed

+3
-6
lines changed

1 file changed

+3
-6
lines changed

security.rst

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1934,12 +1934,9 @@ database and every user is *always* given at least one role: ``ROLE_USER``::
19341934
}
19351935

19361936
This is a nice default, but you can do *whatever* you want to determine which roles
1937-
a user should have. Here are a few guidelines:
1938-
1939-
* Every role **must start with** ``ROLE_`` (otherwise, things won't work as expected)
1940-
1941-
* Other than the above rule, a role is just a string and you can invent what you
1942-
need (e.g. ``ROLE_PRODUCT_ADMIN``).
1937+
a user should have. The only rule is that every role **must start with** ``ROLE_`` -
1938+
otherwise, things won't work as expected. Other than that, a role is just a string
1939+
and you can invent whatever you need (e.g. ``ROLE_PRODUCT_ADMIN``).
19431940

19441941
You'll use these roles next to grant access to specific sections of your site.
19451942

0 commit comments

Comments
 (0)