summaryrefslogtreecommitdiff
path: root/docs/tutorials/wiki
diff options
context:
space:
mode:
authorPatricio Paez <pp@pp.com.mx>2011-05-29 22:03:48 -0500
committerPatricio Paez <pp@pp.com.mx>2011-05-30 18:07:56 -0500
commit6346a4d686a0222349e338a8f5721b06280b0d90 (patch)
tree4cbfd64aa91c713072ed244ee4944f3f2c0b1a12 /docs/tutorials/wiki
parentded6e085fdb6b64d676e96de15e59c0f657c658f (diff)
downloadpyramid-6346a4d686a0222349e338a8f5721b06280b0d90.tar.gz
pyramid-6346a4d686a0222349e338a8f5721b06280b0d90.tar.bz2
pyramid-6346a4d686a0222349e338a8f5721b06280b0d90.zip
Sync Adding Authorization on both wiki tutorials
Diffstat (limited to 'docs/tutorials/wiki')
-rw-r--r--docs/tutorials/wiki/authorization.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/tutorials/wiki/authorization.rst b/docs/tutorials/wiki/authorization.rst
index dbfcb55d5..8781325d2 100644
--- a/docs/tutorials/wiki/authorization.rst
+++ b/docs/tutorials/wiki/authorization.rst
@@ -71,12 +71,12 @@ content:
:linenos:
:language: python
-The ``groupfinder`` function defined here is an authorization policy
+The ``groupfinder`` function defined here is an :term:`authentication policy`
"callback"; it is a callable that accepts a userid and a request. If the
-userid exists in the set of users known by the system, the callback will
+userid exists in the system, the callback will
return a sequence of group identifiers (or an empty sequence if the user
isn't a member of any groups). If the userid *does not* exist in the system,
-the callback will return ``None``. In a production system this data will
+the callback will return ``None``. In a production system, user and group data will
most often come from a database, but here we use "dummy" data to represent
user and groups sources. Note that the ``editor`` user is a member of the
``group:editors`` group in our dummy group data (the ``GROUPS`` data