diff options
| author | Chris McDonough <chrism@agendaless.com> | 2009-12-28 04:12:10 +0000 |
|---|---|---|
| committer | Chris McDonough <chrism@agendaless.com> | 2009-12-28 04:12:10 +0000 |
| commit | 125e9746a5da925243dabf67b2609b556bb9215a (patch) | |
| tree | 2ef52dadcf40f840586293f8cf66e9a11d0f04b0 /docs/narr/security.rst | |
| parent | 48ed96bf621128adf59b225f1c8e33af44bc0594 (diff) | |
| download | pyramid-125e9746a5da925243dabf67b2609b556bb9215a.tar.gz pyramid-125e9746a5da925243dabf67b2609b556bb9215a.tar.bz2 pyramid-125e9746a5da925243dabf67b2609b556bb9215a.zip | |
Adjust for 7.5x9.25in output.
Diffstat (limited to 'docs/narr/security.rst')
| -rw-r--r-- | docs/narr/security.rst | 11 |
1 files changed, 5 insertions, 6 deletions
diff --git a/docs/narr/security.rst b/docs/narr/security.rst index 36469def0..66db64f7f 100644 --- a/docs/narr/security.rst +++ b/docs/narr/security.rst @@ -646,12 +646,11 @@ example, it might be desirable to construct an alternate authorization policy which allows the application to use an authorization mechanism that does not involve :term:`ACL` objects. -:mod:`repoze.bfg` ships with only its single default -:class:`repoze.bfg.authorization.ACLAuthorizationPolicy`, so you'll -need to create your own if you'd like to use a different one. -Creating and using your own authorization policy is a matter of -creating an instance of an object that implements the following -interface: +:mod:`repoze.bfg` ships with only a single default authorization +policy, so you'll need to create your own if you'd like to use a +different one. Creating and using your own authorization policy is a +matter of creating an instance of an object that implements the +following interface: .. code-block:: python |
