| commit | author | age | ||
| 7aae2a | 1 | ``repoze.who`` |
| TS | 2 | ============== |
| 30b996 | 3 | |
| 0cfd9d | 4 | .. image:: https://travis-ci.org/repoze/repoze.who.png?branch=master |
| TS | 5 | :target: https://travis-ci.org/repoze/repoze.who |
| 6 | ||
| 7 | .. image:: https://readthedocs.org/projects/repozewho/badge/?version=latest | |
| 8d27a8 | 8 | :target: http://repozewho.readthedocs.org/en/latest/ |
| 0cfd9d | 9 | :alt: Documentation Status |
| TS | 10 | |
| 30b996 | 11 | Overview |
| TS | 12 | -------- |
| fdbab9 | 13 | |
| 7141c7 | 14 | ``repoze.who`` is an identification and authentication framework |
| 30b996 | 15 | for arbitrary WSGI applications. ``repoze.who`` can be configured |
| TS | 16 | either as WSGI middleware or as an API for use by an application. |
| fdbab9 | 17 | |
| 7141c7 | 18 | ``repoze.who`` is inspired by Zope 2's Pluggable Authentication |
| TS | 19 | Service (PAS) (but ``repoze.who`` is not dependent on Zope in any |
| 25ac2e | 20 | way; it is useful for any WSGI application). It provides no facility |
| CM | 21 | for authorization (ensuring whether a user can or cannot perform the |
| 22 | operation implied by the request). This is considered to be the | |
| 23 | domain of the WSGI application. | |
