summaryrefslogtreecommitdiff
path: root/docs/tutorials/bfgwiki/authorization.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/tutorials/bfgwiki/authorization.rst')
-rw-r--r--docs/tutorials/bfgwiki/authorization.rst13
1 files changed, 7 insertions, 6 deletions
diff --git a/docs/tutorials/bfgwiki/authorization.rst b/docs/tutorials/bfgwiki/authorization.rst
index bd4e80206..e493852ec 100644
--- a/docs/tutorials/bfgwiki/authorization.rst
+++ b/docs/tutorials/bfgwiki/authorization.rst
@@ -29,12 +29,13 @@ the policy, and pass it as the ``authentication_policy`` argument to
the ``make_app`` function. The first positional argument of an
``AuthTktAuthenticationPolicy`` is a secret used to encrypt cookie
data. Its second argument ("callback") should be a callable that
-accepts a userid. If the userid exists in the system, the callback
-should 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 should return ``None``. We'll use
-"dummy" data to represent user and groups sources. When we're done,
-your application's ``run.py`` will look like this.
+accepts a userid ana a request. If the userid exists in the system,
+the callback should 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 should return
+``None``. We'll use "dummy" data to represent user and groups
+sources. When we're done, your application's ``run.py`` will look
+like this.
.. literalinclude:: src/authorization/tutorial/run.py
:linenos: