PKG-INFO 32 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743
  1. Metadata-Version: 1.1
  2. Name: repoze.who
  3. Version: 2.3
  4. Summary: repoze.who is an identification and authentication framework for WSGI.
  5. Home-page: http://www.repoze.org
  6. Author: Agendaless Consulting
  7. Author-email: repoze-dev@lists.repoze.org
  8. License: BSD-derived (http://www.repoze.org/LICENSE.txt)
  9. Description: ``repoze.who``
  10. ==============
  11. .. image:: https://travis-ci.org/repoze/repoze.who.png?branch=master
  12. :target: https://travis-ci.org/repoze/repoze.who
  13. .. image:: https://readthedocs.org/projects/repozewho/badge/?version=latest
  14. :target: http://repozewho.readthedocs.org/en/latest/
  15. :alt: Documentation Status
  16. Overview
  17. --------
  18. ``repoze.who`` is an identification and authentication framework
  19. for arbitrary WSGI applications. ``repoze.who`` can be configured
  20. either as WSGI middleware or as an API for use by an application.
  21. ``repoze.who`` is inspired by Zope 2's Pluggable Authentication
  22. Service (PAS) (but ``repoze.who`` is not dependent on Zope in any
  23. way; it is useful for any WSGI application). It provides no facility
  24. for authorization (ensuring whether a user can or cannot perform the
  25. operation implied by the request). This is considered to be the
  26. domain of the WSGI application.
  27. repoze.who Changelog
  28. ====================
  29. 2.3 (2016-05-31)
  30. ----------------
  31. - Add support for Python 3.4, Python 3.5, and PyPy3.
  32. - Drop support for Python 2.6 and 3.2.
  33. - ``middleware``: avoid passing extracted ``identity`` to ``remember``
  34. during egress (the app may have called ``api.forget()``). See #21.
  35. - ``_auth_tkt`` / ``plugins.auth_tkt``: add support for any hash algorithm
  36. supported by the ``hashlib`` module in Python's standard library.
  37. Fixes #22 via #23.
  38. - ``plugins.auth_tkt``: Fix storage of "userdata" to save dict. Fixes
  39. #14 via #18.
  40. - middleware: avoid UnboundLocalError when wrapped generater yields no
  41. items. See: http://bugs.repoze.org/issue184
  42. - Make cookie expiration date RFC-2616 compliant (independent of locale,
  43. including 'GMT' zone). See #11.
  44. 2.2 (2013-05-17)
  45. ----------------
  46. - Parse INI-file configuration using ``SafeConfigParser``: allows
  47. escaping the ``'%'`` so that e.g. a query template using for a DB-API
  48. connection using ``pyformat`` preserves the template.
  49. - Added support for Python 3.3, PyPy.
  50. 2.1 (2013-03-20)
  51. ----------------
  52. - ``_compat`` module: tolerate missing ``CONTENT_TYPE`` key in the WSGI
  53. environment. Thanks to Dag Hoidal for the patch.
  54. - ``htpasswd`` plugin: add a ``sha1_check`` checker function (the ``crypt``
  55. module is not available on Windows). Thanks to Chandrashekar Jayaraman
  56. for the patch.
  57. - Documentation typo fixes from Carlos de la Guardia and Atsushi Odagiri.
  58. 2.1b1 (2012-11-05)
  59. ------------------
  60. - Ported to Py3k using the "compatible subset" mode.
  61. - Dropped support for Python < 2.6.x.
  62. - Dropped dependency on Paste (forking some code from it).
  63. - Added dependency on WebOb instead.
  64. Thanks to Atsushi Odagiri (aodag) for the initial effort.
  65. 2.0 (2011-09-28)
  66. ----------------
  67. - ``auth_tkt`` plugin: strip any port number from the 'Domain' of generated
  68. cookies. http://bugs.repoze.org/issue66
  69. - Further harden middleware, calling ``close()`` on the iterable even if
  70. raising an exception for a missing challenger.
  71. http://bugs.repoze.org/issue174
  72. 2.0b1 (2011-05-24)
  73. ------------------
  74. - Enabled standard use of logging module's configuration mechanism.
  75. See http://docs.python.org/dev/howto/logging.html#configuring-logging-for-a-library
  76. Thanks to jgoldsmith for the patch: http://bugs.repoze.org/issue178
  77. - ``repoze.who.plugins.htpasswd``: defend against timing-based attacks.
  78. 2.0a4 (2011-02-02)
  79. ------------------
  80. - Ensure that the middleware calls ``close()`` (if it exists) on the
  81. iterable returned from thw wrapped application, as required by PEP 333.
  82. http://bugs.repoze.org/issue174
  83. - Make ``make_api_factory_with_config`` tolerant of invalid filenames /
  84. content for the config file: in such cases, the API factory will have
  85. *no* configured plugins or policies: it will only be useful for retrieving
  86. the API from an environment populated by middleware.
  87. - Fix bug in ``repoze.who.api`` where the ``remember()`` or ``forget()``
  88. methods could return a None if the identifier plugin returned a None.
  89. - Fix ``auth_tkt`` plugin to not hand over tokens as strings to paste. See
  90. http://lists.repoze.org/pipermail/repoze-dev/2010-November/003680.html
  91. - Fix ``auth_tkt`` plugin to add "secure" and "HttpOnly" to cookies when
  92. configured with ``secure=True``: these attributes prevent the browser from
  93. sending cookies over insecure channels, which could be vulnerable to some
  94. XSS attacks.
  95. - Avoid propagating unicode 'max_age' value into cookie headers. See
  96. https://bugs.launchpad.net/bugs/674123 .
  97. - Added a single-file example BFG application demonstrating the use of
  98. the new 'login' and 'logout' methods of the API object.
  99. - Add ``login`` and ``logout`` methods to the ``repoze.who.api.API`` object,
  100. as a convenience for application-driven login / logout code, which would
  101. otherwise need to use private methods of the API, and reach down into
  102. its plugins.
  103. 2.0a3 (2010-09-30)
  104. ------------------
  105. - Deprecated the following plugins, moving their modules, tests, and docs
  106. to a new project, ``repoze.who.deprecatedplugins``:
  107. - ``repoze.who.plugins.cookie.InsecureCookiePlugin``
  108. - ``repoze.who.plugins.form.FormPlugin``
  109. - ``repoze.who.plugins.form.RedirectingFormPlugin``
  110. - Made the ``repoze.who.plugins.cookie.InsecureCookiePlugin`` take a
  111. ``charset`` argument, and use to to encode / decode login and password.
  112. See http://bugs.repoze.org/issue155
  113. - Updated ``repoze.who.restrict`` to return headers as a list, to keep
  114. ``wsgiref`` from complaining.
  115. - Helped default request classifier cope with xml submissions with an
  116. explicit charset defined: http://bugs.repoze.org/issue145 (Lorenzo
  117. M. Catucci)
  118. - Corrected the handling of type and subtype when matching an XML post
  119. to ``xmlpost`` in the default classifier, which, according to RFC
  120. 2045, must be matched case-insensitively:
  121. http://bugs.repoze.org/issue145 (Lorenzo M. Catucci)
  122. - Added ``repoze.who.config:make_api_factory_with_config``, a convenience
  123. method for applications which want to set up their own API Factory from
  124. a configuration file.
  125. - Fixed example call to ``repoze.who.config:make_middleware_with_config``
  126. (added missing ``global_config`` argument). See
  127. http://bugs.repoze.org/issue114
  128. 2.0a2 (2010-03-25)
  129. ------------------
  130. Bugs Fixed
  131. ~~~~~~~~~~
  132. - Fixed failure to pass substution values in log message string formatting
  133. for ``repoze.who.api:API.challenge``. Fix included adding tests for all
  134. logging done by the API object. See http://bugs.repoze.org/issue122
  135. Backward Incompatibilities
  136. ~~~~~~~~~~~~~~~~~~~~~~~~~~
  137. - Adjusted logging level for some lower-level details from ``info``
  138. to ``debug``.
  139. 2.0a1 (2010-02-24)
  140. ------------------
  141. Features
  142. ~~~~~~~~
  143. - Restored the ability to create the middleware using the old ``classifier``
  144. argument. That argument is now a deprecated-but-will-work-forever alias for
  145. ``request_classifier``.
  146. - The ``auth_tkt`` plugin now implements the ``IAuthenticator`` interface,
  147. and should normally be used both as an ``IIdentifier`` and an
  148. ``IAuthenticator``.
  149. - Factored out the API of the middleware object to make it useful from
  150. within the application. Applications using ``repoze.who``` now fall into
  151. one of three catgeories:
  152. - "middleware-only" applications are configured with middleware, and
  153. use either ``REMOTE_USER`` or ``repoze.who.identity`` from the environment
  154. to determing the authenticated user.
  155. - "bare metal" applications use no ``repoze.who`` middleware at all:
  156. instead, they configure and an ``APIFactory`` object at startup, and
  157. use it to create an ``API`` object when needed on a per-request basis.
  158. - "hybrid" applications are configured with ``repoze.who`` middleware,
  159. but use a new library function to fetch the ``API`` object from the
  160. environ, e.g. to permit calling ``remember`` after a signup or successful
  161. login.
  162. Bugs Fixed
  163. ~~~~~~~~~~
  164. - Fix http://bugs.repoze.org/issue102: when no challengers existed,
  165. logging would cause an exception.
  166. - Remove ``ez_setup.py`` and dependency on it in setup.py (support
  167. distribute).
  168. Backward Incompatibilities
  169. ~~~~~~~~~~~~~~~~~~~~~~~~~~
  170. - The middleware used to allow identifier plugins to "pre-authenticate"
  171. an identity. This feature is no longer supported: the ``auth_tkt``
  172. plugin, which used to use the feature, is now configured to work as
  173. an authenticator plugin (as well as an identifier).
  174. - The ``repoze.who.middleware:PluggableAuthenticationMiddleware`` class
  175. no longer has the following (non-API) methods (now made API methods
  176. of the ``repoze.who.api:API`` class):
  177. - ``add_metadata``
  178. - ``authenticate``
  179. - ``challenge``
  180. - ``identify``
  181. - The following (non-API) functions moved from ``repoze.who.middleware`` to
  182. ``repoze.who.api``:
  183. - ``make_registries``
  184. - ``match_classification``
  185. - ``verify``
  186. 1.0.18 (2009-11-05)
  187. -------------------
  188. - Issue #104: AuthTkt plugin was passing an invalid cookie value in
  189. headers from ``forget``, and was not setting the ``Max-Age`` and
  190. ``Expires`` attributes of those cookies.
  191. 1.0.17 (2009-11-05)
  192. -------------------
  193. - Fixed the ``repoze.who.plugins.form.make_plugin`` factory's ``formcallable``
  194. argument handling, to allow passing in a dotted name (e.g., from a config
  195. file).
  196. 1.0.16 (2009-11-04)
  197. -------------------
  198. - Exposed ``formcallable`` argument for ``repoze.who.plugins.form.FormPlugin``
  199. to the callers of the ``repoze.who.plugins.form.make_plugin`` factory.
  200. Thanks to Roland Hedburg for the report.
  201. - Fixed an issue that caused the following symptom when using the
  202. ini configuration parser::
  203. TypeError: _makePlugin() got multiple values for keyword argument 'name'
  204. See http://bugs.repoze.org/issue92 for more details. Thanks to vaab
  205. for the bug report and initial fix.
  206. 1.0.15 (2009-06-25)
  207. -------------------
  208. - If the form post value ``max_age`` exists while in the ``identify``
  209. method is handling the ``login_handler_path``, pass the max_age
  210. value in the returned identity dictionary as ``max_age``. See the
  211. below bullet point for why.
  212. - If the ``identity`` dict passed to the ``auth_tkt`` ``remember``
  213. method contains a ``max_age`` key with a string (or integer) value,
  214. treat it as a cue to set the ``Max-Age`` and ``Expires`` headers in
  215. the returned cookies. The cookie ``Max-Age`` is set to the value
  216. and the ``Expires`` is computed from the current time.
  217. 1.0.14 (2009-06-17)
  218. -------------------
  219. - Fix test breakage on Windows. See http://bugs.repoze.org/issue79 .
  220. - Documented issue with using ``include_ip`` setting in the ``auth_tkt``
  221. plugin. See http://bugs.repoze.org/issue81 .
  222. - Added 'passthrough_challenge_decider', which avoids re-challenging 401
  223. responses which have been "pre-challenged" by the application.
  224. - One-hundred percent unit test coverage.
  225. - Add ``timeout`` and ``reissue_time`` arguments to the auth_tkt
  226. identifier plugin, courtesty of Paul Johnston.
  227. - Add a ``userid_checker`` argument to the auth_tkt identifier plugin,
  228. courtesty of Gustavo Narea.
  229. If ``userid_checker`` is provided, it must be a dotted Python name
  230. that resolves to a function which accepts a userid and returns a
  231. boolean True or False, indicating whether that user exists in a
  232. database. This is a workaround. Due to a design bug in repoze.who,
  233. the only way who can check for user existence is to use one or more
  234. IAuthenticator plugin ``authenticate`` methods. If an
  235. IAuthenticator's ``authenticate`` method returns true, it means that
  236. the user exists. However most IAuthenticator plugins expect *both*
  237. a username and a password, and will return False unconditionally if
  238. both aren't supplied. This means that an authenticator can't be
  239. used to check if the user "only" exists. The identity provided by
  240. an auth_tkt does not contain a password to check against. The
  241. actual design bug in repoze.who is this: when a user presents
  242. credentials from an auth_tkt, he is considered "preauthenticated".
  243. IAuthenticator.authenticate is just never called for a
  244. "preauthenticated" identity, which works fine, but it means that the
  245. user will be considered authenticated even if you deleted the user's
  246. record from whatever database you happen to be using. However, if
  247. you use a userid_checker, you can ensure that a user exists for the
  248. auth_tkt supplied userid. If the userid_checker returns False, the
  249. auth_tkt credentials are considered "no good".
  250. 1.0.13 (2009-04-24)
  251. -------------------
  252. - Added a paragraph to ``IAuthenticator`` docstring, documenting that plugins
  253. are allowed to add keys to the ``identity`` dictionary (e.g., to save a
  254. second database query in an ``IMetadataProvider`` plugin).
  255. - Patch supplied for issue #71 (http://bugs.repoze.org/issue71)
  256. whereby a downstream app can return a generator, relying on an
  257. upstream component to call start_response. We do this because the
  258. challenge decider needs the status and headers to decide what to do.
  259. 1.0.12 (2009-04-19)
  260. -------------------
  261. - auth_tkt plugin tried to append REMOTE_USER_TOKENS data to
  262. existing tokens data returned by auth_tkt.parse_tkt; this was
  263. incorrect; just overwrite.
  264. - Extended auth_tkt plugin factory to allow passing secret in a separate
  265. file from the main config file. See http://bugs.repoze.org/issue40 .
  266. 1.0.11 (2009-04-10)
  267. -------------------
  268. - Fix auth_tkt plugin; cookie values are now quoted, making it possible
  269. to put spaces and other whitespace, etc in usernames. (thanks to Michael
  270. Pedersen).
  271. - Fix corner case issue of an exception raised when attempting to log
  272. when there are no identifiers or authenticators.
  273. 1.0.10 (2009-01-23)
  274. -------------------
  275. - The RedirectingFormPlugin now passes along SetCookie headers set
  276. into the response by the application within the NotFound response
  277. (fixes TG2 "flash" issue).
  278. 1.0.9 (2008-12-18)
  279. ------------------
  280. - The RedirectingFormPlugin now attempts to find a header named
  281. ``X-Authentication-Failure-Reason`` among the response headers set
  282. by the application when a challenge is issued. If a value for this
  283. header exists (and is non-blank), the value is attached to the
  284. redirect URL's query string as the ``reason`` parameter (or a
  285. user-settable key). This makes it possible for downstream
  286. applications to issue a response that initiates a challenge with
  287. this header and subsequently display the reason in the login form
  288. rendered as a result of the challenge.
  289. 1.0.8 (2008-12-13)
  290. ------------------
  291. - The ``PluggableAuthenticationMiddleware`` constructor accepts a
  292. ``log_stream`` argument, which is typically a file. After this
  293. release, it can also be a PEP 333 ``Logger`` instance; if it is a
  294. PEP 333 ``Logger`` instance, this logger will be used as the
  295. repoze.who logger (instead of one being constructed by the
  296. middleware, as was previously always the case). When the
  297. ``log_stream`` argument is a PEP 333 Logger object, the
  298. ``log_level`` argument is ignored.
  299. 1.0.7 (2008-08-28)
  300. ------------------
  301. - ``repoze.who`` and ``repoze.who.plugins`` were not added to the
  302. ``namespace_packages`` list in setup.py, potentially making 1.0.6 a
  303. brownbag release, given that making these packages namespace
  304. packages was the only reason for its release.
  305. 1.0.6 (2008-08-28)
  306. ------------------
  307. - Make repoze.who and repoze.who.plugins into namespace packages
  308. mainly so we can allow plugin authors to distribute packages in the
  309. repoze.who.plugins namespace.
  310. 1.0.5 (2008-08-23)
  311. ------------------
  312. - Fix auth_tkt plugin to set the same cookies in its ``remember``
  313. method that it does in its ``forget`` method. Previously, logging
  314. out and relogging back in to a site that used auth_tkt identifier
  315. plugin was slightly dicey and would only work sometimes.
  316. - The FormPlugin plugin has grown a redirect-on-unauthorized feature.
  317. Any response from a downstream application that causes a challenge
  318. and includes a Location header will cause a redirect to the value of
  319. the Location header.
  320. 1.0.4 (2008-08-22)
  321. ------------------
  322. - Added a key to the '[general]' config section: ``remote_user_key``.
  323. If you use this key in the config file, it tells who to 1) not
  324. perform any authentication if it exists in the environment during
  325. ingress and 2) to set the key in the environment for the downstream
  326. app to use as the REMOTE_USER variable. The default is
  327. ``REMOTE_USER``.
  328. - Using unicode user ids in combination with the auth_tkt plugin would
  329. cause problems under mod_wsgi.
  330. - Allowed 'cookie_path' argument to InsecureCookiePlugin (and config
  331. constructor). Thanks to Gustavo Narea.
  332. 1.0.3 (2008-08-16)
  333. ------------------
  334. - A bug in the middleware's ``authenticate`` method made it impossible
  335. to authenticate a user with a userid that was null (e.g. 0, False),
  336. which are valid identifiers. The only invalid userid is now None.
  337. - Applied patch from Olaf Conradi which logs an error when an invalid
  338. filename is passed to the HTPasswdPlugin.
  339. 1.0.2 (2008-06-16)
  340. ------------------
  341. - Fix bug found by Chris Perkins: the auth_tkt plugin's "remember"
  342. method didn't handle userids which are Python "long" instances
  343. properly. Symptom: TypeError: cannot concatenate 'str' and 'long'
  344. objects in "paste.auth.auth_tkt".
  345. - Added predicate-based "restriction" middleware support
  346. (repoze.who.restrict), allowing configuratio-driven authorization as
  347. a WSGI filter. One example predicate, 'authenticated_predicate', is
  348. supplied, which requires that the user be authenticated either via
  349. 'REMOTE_USER' or via 'repoze.who.identity'. To use the filter to
  350. restrict access::
  351. [filter:authenticated_only]
  352. use = egg:repoze.who#authenticated
  353. or::
  354. [filter:some_predicate]
  355. use = egg:repoze.who#predicate
  356. predicate = my.module:some_predicate
  357. some_option = a value
  358. 1.0.1 (2008-05-24)
  359. ------------------
  360. - Remove dependency-link to dist.repoze.org to prevent easy_install
  361. from inserting that path into its search paths (the dependencies are
  362. available from PyPI).
  363. 1.0 (2008-05-04)
  364. -----------------
  365. - The plugin at plugins.form.FormPlugin didn't redirect properly after
  366. collecting identification information. Symptom: a downstream app
  367. would receive a POST request with a blank body, which would
  368. sometimes result in a Bad Request error.
  369. - Fixed interface declarations of
  370. 'classifiers.default_request_classifier' and
  371. 'classifiers.default_password_compare'.
  372. - Added actual config-driven middleware factory,
  373. 'config.make_middleware_with_config'
  374. - Removed fossilized 'who_conf' argument from plugin factory functions.
  375. - Added ConfigParser-based WhoConfig, implementing the spec outlined at
  376. http://www.plope.com/static/misc/sphinxtest/intro.html#middleware-configuration-via-config-file,
  377. with the following changes:
  378. - "Bare" plugins (requiring no configuration options) may be specified
  379. as either egg entry points (e.g., 'egg:distname#entry_point_name') or
  380. as dotted-path-with-colon (e.g., 'dotted.name:object_id').
  381. - Therefore, the separator between a plugin and its classifier is now
  382. a semicolon, rather than a colon. E.g.::
  383. [plugins:id_plugin]
  384. use = egg:another.package#identify_with_frobnatz
  385. frobnatz = baz
  386. [identifiers]
  387. plugins =
  388. egg:my.egg#identify;browser
  389. dotted.name:identifier
  390. id_plugin
  391. 0.9.1 (2008-04-27)
  392. ------------------
  393. - Fix auth_tkt plugin to be able to encode and decode integer user
  394. ids.
  395. 0.9 (2008-04-01)
  396. ----------------
  397. - Fix bug introduced in FormPlugin in 0.8 release (rememberer headers
  398. not set).
  399. - Add PATH_INFO to started and ended log info.
  400. - Add a SQLMetadataProviderPlugin (in plugins/sql).
  401. - Change constructor of SQLAuthenticatorPlugin: it now accepts only
  402. "query", "conn_factory", and "compare_fn". The old constructor
  403. accepted a DSN, but some database systems don't use DBAPI DSNs. The
  404. new constructor accepts no DSN; the conn_factory is assumed to do
  405. all the work to make a connection, including knowing the DSN if one
  406. is required. The "conn_factory" should return something that, when
  407. called with no arguments, returns a database connection.
  408. - The "make_plugin" helper in plugins/sql has been renamed
  409. "make_authenticator_plugin". When called, this helper will return a
  410. SQLAuthenticatorPlugin. A bit of helper logic in the
  411. "make_authenticator_plugin" allows a connection factory to be
  412. computed. The top-level callable referred to by conn_factory in
  413. this helper should return a function that, when called with no
  414. arguments, returns a datbase connection. The top-level callable
  415. itself is called with "who_conf" (global who configuration) and any
  416. number of non-top-level keyword arguments as they are passed into
  417. the helper, to allow for a DSN or URL or whatever to be passed in.
  418. - A "make_metatata_plugin" helper has been added to plugins/sql. When
  419. called, this will make a SQLMetadataProviderPlugin. See the
  420. implementation for details. It is similar to the
  421. "make_authenticator_plugin" helper.
  422. 0.8 (2008-03-27)
  423. ----------------
  424. - Add a RedirectingFormIdentifier plugin. This plugin is willing to
  425. redirect to an external (or downstream application) login form to
  426. perform identification. The external login form must post to the
  427. "login_handler_path" of the plugin (optimally with a "came_from"
  428. value to tell the plugin where to redirect the response to if the
  429. authentication works properly). The "logout_handler_path" of this
  430. plugin can be visited to perform a logout. The "came_from" value
  431. also works there.
  432. - Identifier plugins are now permitted to set a key in the environment
  433. named 'repoze.who.application' on ingress (in 'identify'). If an
  434. identifier plugin does so, this application is used instead of the
  435. "normal" downstream application. This feature was added to more
  436. simply support the redirecting form identifier plugin.
  437. 0.7 (2008-03-26)
  438. ----------------
  439. - Change the IMetadataProvider interface: this interface used to have
  440. a "metadata" method which returned a dictionary. This method is not
  441. part of that API anymore. It's been replaced with an "add_metadata"
  442. method which has the signature::
  443. def add_metadata(environ, identity):
  444. """
  445. Add metadata to the identity (which is a dictionary)
  446. """
  447. The return value is ignored. IMetadataProvider plugins are now
  448. assumed to be responsible for 'scribbling' directly on the identity
  449. that is passed in (it's a dictionary). The user id can always be
  450. retrieved from the identity via identity['repoze.who.userid'] for
  451. metadata plugins that rely on that value.
  452. 0.6 (2008-03-20)
  453. ----------------
  454. - Renaming: repoze.pam is now repoze.who
  455. - Bump ez_setup.py version.
  456. - Add IMetadataProvider plugin type. Chris says 'Whit rules'.
  457. 0.5 (2008-03-09)
  458. ----------------
  459. - Allow "remote user key" (default: REMOTE_USER) to be overridden
  460. (pass in remote_user_key to middleware constructor).
  461. - Allow form plugin to override the default form.
  462. - API change: IIdentifiers are no longer required to put both 'login'
  463. and 'password' in a returned identity dictionary. Instead, an
  464. IIdentifier can place arbitrary key/value pairs in the identity
  465. dictionary (or return an empty dictionary).
  466. - API return value change: the "failure" identity which IIdentifiers
  467. return is now None rather than an empty dictionary.
  468. - The IAuthenticator interface now specifies that IAuthenticators must
  469. not raise an exception when evaluating an identity that does not
  470. have "expected" key/value pairs (e.g. when an IAuthenticator that
  471. expects login and password inspects an identity returned by an
  472. IP-based auth system which only puts the IP address in the
  473. identity); instead they fail gracefully by returning None.
  474. - Add (cookie) "auth_tkt" identification plugin.
  475. - Stamp identity dictionaries with a userid by placing a key named
  476. 'repoze.pam.userid' into the identity for each authenticated
  477. identity.
  478. - If an IIdentifier plugin inserts a 'repoze.pam.userid' key into the
  479. identity dictionary, consider this identity "preauthenticated". No
  480. authenticator plugins will be asked to authenticate this identity.
  481. This is designed for things like the recently added auth_tkt plugin,
  482. which embeds the user id into the ticket. This effectively alllows
  483. an IIdentifier plugin to become an IAuthenticator plugin when
  484. breaking apart the responsibility into two separate plugins is
  485. "make-work". Preauthenticated identities will be selected first
  486. when deciding which identity to use for any given request.
  487. - Insert a 'repoze.pam.identity' key into the WSGI environment on
  488. ingress if an identity is found. Its value will be the identity
  489. dictionary related to the identity selected by repoze.pam on
  490. ingress. Downstream consumers are allowed to mutate this
  491. dictionary; this value is passed to "remember" and "forget", so its
  492. main use is to do a "credentials reset"; e.g. a user has changed his
  493. username or password within the application, but we don't want to
  494. force him to log in again after he does so.
  495. 0.4 (03-07-2008)
  496. ----------------
  497. - Allow plugins to specify a classifiers list per interface (instead
  498. of a single classifiers list per plugin).
  499. 0.3 (03-05-2008)
  500. ----------------
  501. - Make SQLAuthenticatorPlugin's default_password_compare use hexdigest
  502. sha instead of base64'ed binary sha for simpler conversion.
  503. 0.2 (03-04-2008)
  504. ----------------
  505. - Added SQLAuthenticatorPlugin (see plugins/sql.py).
  506. 0.1 (02-27-2008)
  507. ----------------
  508. - Initial release (no configuration file support yet).
  509. Keywords: web application server wsgi zope
  510. Platform: UNKNOWN
  511. Classifier: Development Status :: 5 - Production/Stable
  512. Classifier: Intended Audience :: Developers
  513. Classifier: Programming Language :: Python :: 2
  514. Classifier: Programming Language :: Python :: 2.7
  515. Classifier: Programming Language :: Python :: 3
  516. Classifier: Programming Language :: Python :: 3.3
  517. Classifier: Programming Language :: Python :: 3.4
  518. Classifier: Programming Language :: Python :: 3.5
  519. Classifier: Programming Language :: Python :: Implementation :: CPython
  520. Classifier: Programming Language :: Python :: Implementation :: PyPy
  521. Classifier: Topic :: Internet :: WWW/HTTP
  522. Classifier: Topic :: Internet :: WWW/HTTP :: Dynamic Content
  523. Classifier: Topic :: Internet :: WWW/HTTP :: WSGI
  524. Classifier: Topic :: Internet :: WWW/HTTP :: WSGI :: Application