summaryrefslogtreecommitdiff
path: root/docs/designdefense.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/designdefense.rst')
-rw-r--r--docs/designdefense.rst5
1 files changed, 2 insertions, 3 deletions
diff --git a/docs/designdefense.rst b/docs/designdefense.rst
index 0f452ffde..566ad1f5e 100644
--- a/docs/designdefense.rst
+++ b/docs/designdefense.rst
@@ -181,15 +181,14 @@ developer needs to understand a ZCA concept or API during the creation of a
Instead the framework hides the presence of the ZCA registry behind
special-purpose API functions that *do* use ZCA APIs. Take for example the
-``pyramid.security.authenticated_userid`` function, which returns the userid
+``request.authenticated_userid`` function, which returns the userid
present in the current request or ``None`` if no userid is present in the
current request. The application developer calls it like so:
.. code-block:: python
:linenos:
- from pyramid.security import authenticated_userid
- userid = authenticated_userid(request)
+ userid = request.authenticated_userid
They now have the current user id.