1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
|
Metadata-Version: 1.0
Name: AuthKit
Version: 0.4.1dev-r139
Summary: An authentication and authorization toolkit for WSGI applications and frameworks
Home-page: http://authkit.org/
Author: James Gardner
Author-email: james@pythonweb.org
License: MIT
Description:
AuthKit
+++++++
.. contents ::
Summary
=======
* Built for WSGI applications and middleware
* Sophisticated and extensible permissions system
* Built in support for HTTP basic, HTTP digest, form, cookie and OpenID
authentication methods plus others
* Easily define users, passwords and roles
* Designed to be totally extensible so you can use the components to integrate
with a database, LDAP connection or your own custom system
* Plays nicely with the `Pylons <http://pylonshq.com>`_ web framework
There is also a `development version
<http://authkit.org/svn/AuthKit/trunk#egg=AuthKit-dev>`_.
Get Started
===========
* `Download and Installation <http://python.org/pypi/AuthKit/0.4.0>`_
* `Pylons Book <http://pylonsbook.com>`_ (the two chapters on *Authentication and
Authorization* and *Advanced AuthKit* form the AuthKit 0.4 documentation)
* `Module Reference <http://authkit.org/docs/0.4/module-index.html>`_
* `AuthKit Cookbook <http://wiki.pylonshq.com/display/authkitcookbook/Home>`_
* `Trac <http://authkit.org/trac>`_ - Tickets, Wiki, Subversion
* `Examples <http://authkit.org/trac/browser/AuthKit/trunk/examples>`_
Author
======
`James Gardner <http://jimmyg.org/>`_ james at pythonweb dot org
Development sponsored by `3aims <http://3aims.com/>`_ and
`Prometheus Research <http://www.prometheusresearch.com/>`_.
Changes
=======
0.4.1 (**svn**)
* Added a user management api_version attribute and changed the API so that
the users object is set up on each request and recieves an environ
argument.
* OpenID middleware now no longer sets up beaker middleware itself. This
should now be done manually in the middleware stack. See the example in
examples/docs/open_id.py
* OpenID support now upgraded to use 2.0 (from Dalius Dobravolskas)
* Fixed encrypt typo with postgres users driver
* The cookie middleware now has a nouserincookie option which forces the
middleware to store the username in a Beaker session rather than in plain
text in the cookie. See examples/docs/form_no_user_in_cookie.py for an
example of its use.
* Form authentication method now defaults to 200 OK rather than 401 when
the sign in form is displayed so that it works with Safari 3 Beta.
* The cookie middleware Bad Ticket page now also uses 200 OK, also to
support Safari 3 Beta.
* The cookie middleware bad ticket now logs to debug rather than error to
avoid the ``No handlers could be found for logger
"authkit.authenticate.cookie"`` message you get with a bad cookie if no
error logging is specifically set up.
* Added a user management api_version attribute and changed the API so that
the users object is set up on each request and recieves an environ
argument.
* Fixed encrypt typo with postgres users driver
* Renamed the config_paste option to app_conf in authenticate middleware. If
you get an "No authkit.setup.method was specified" error when you are sure
it is specified, this might be why.
0.4.0
* Added support for encrypted passwords
* Fixed the IE7 bug in digest middleware
* Adding SSO sub-directory, redirecting API, and CAS auth handler.
* Fixed binding check to return none, instead of throwing an Exception (for
performance reasons).
* Moved start_response check outside of app_iter consumption since it must be
called by this point to comply with WSGI.
* Fixed consumption app iter in multi, loading entire response into ram.
* Adding changelog
* Added IP and Time based permission objects
* Started unit tests
* Extended the user management API and added SQLAlchemy driver and example
* Restructured the authenticate middleware into induvidual pluggable components
* Simplified the configuration file system
* Added OpenID dependencies
* Removed the larger SQLAlchemy based demos
* The cookie module uses ``authkit`` as a default cookie name, not ``auth_tkt``.
Any code which does anything manually with this cookie needs the name changing
if it wasn't explicitly set to ``auth_tkt`` in the config file.
0.3.0pre5
* Changed the arguments to the authkit.authenticate.middleware() factory. You
will need to update your middleware setup to use app_conf instead of
config_paste for the app_conf dictionary.
0.3
* Re-written from scratch to be a modular toolkit for building your own auth
framework rather than an all-in-one solution.
0.2
* Re-written from scratch so to use SQLAlchemy only, old driver system considered
unnecessary and limiting. Also doesn't fit in with current Pylons
best-practice.
0.1
* Based on the web.auth 0.6 module from www.pythonweb.org, support for SQLObject
driver included
License
=======
Copyright (c) Copyright 2005-2007 James Gardner <james at pythonweb dot org>
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
Download
========
Platform: UNKNOWN
|
