Repoze.who

Latest version: v3.0.0

Safety actively analyzes 628918 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 6 of 7

1.0.1

------------------

- Remove dependency-link to dist.repoze.org to prevent easy_install
from inserting that path into its search paths (the dependencies are
available from PyPI).

1.0

-----------------

- The plugin at plugins.form.FormPlugin didn't redirect properly after
collecting identification information. Symptom: a downstream app
would receive a POST request with a blank body, which would
sometimes result in a Bad Request error.

- Fixed interface declarations of
'classifiers.default_request_classifier' and
'classifiers.default_password_compare'.

- Added actual config-driven middleware factory,
'config.make_middleware_with_config'

- Removed fossilized 'who_conf' argument from plugin factory functions.

- Added ConfigParser-based WhoConfig, implementing the spec outlined at
http://www.plope.com/static/misc/sphinxtest/intro.html#middleware-configuration-via-config-file,
with the following changes:

- "Bare" plugins (requiring no configuration options) may be specified
as either egg entry points (e.g., 'egg:distnameentry_point_name') or
as dotted-path-with-colon (e.g., 'dotted.name:object_id').

- Therefore, the separator between a plugin and its classifier is now
a semicolon, rather than a colon. E.g.::

[plugins:id_plugin]
use = egg:another.packageidentify_with_frobnatz
frobnatz = baz

[identifiers]
plugins =
egg:my.eggidentify;browser
dotted.name:identifier
id_plugin

0.9.1

------------------

- Fix auth_tkt plugin to be able to encode and decode integer user
ids.

0.9

----------------

- Fix bug introduced in FormPlugin in 0.8 release (rememberer headers
not set).

- Add PATH_INFO to started and ended log info.

- Add a SQLMetadataProviderPlugin (in plugins/sql).

- Change constructor of SQLAuthenticatorPlugin: it now accepts only
"query", "conn_factory", and "compare_fn". The old constructor
accepted a DSN, but some database systems don't use DBAPI DSNs. The
new constructor accepts no DSN; the conn_factory is assumed to do
all the work to make a connection, including knowing the DSN if one
is required. The "conn_factory" should return something that, when
called with no arguments, returns a database connection.

- The "make_plugin" helper in plugins/sql has been renamed
"make_authenticator_plugin". When called, this helper will return a
SQLAuthenticatorPlugin. A bit of helper logic in the
"make_authenticator_plugin" allows a connection factory to be
computed. The top-level callable referred to by conn_factory in
this helper should return a function that, when called with no
arguments, returns a datbase connection. The top-level callable
itself is called with "who_conf" (global who configuration) and any
number of non-top-level keyword arguments as they are passed into
the helper, to allow for a DSN or URL or whatever to be passed in.

- A "make_metatata_plugin" helper has been added to plugins/sql. When
called, this will make a SQLMetadataProviderPlugin. See the
implementation for details. It is similar to the
"make_authenticator_plugin" helper.

0.8

----------------

- Add a RedirectingFormIdentifier plugin. This plugin is willing to
redirect to an external (or downstream application) login form to
perform identification. The external login form must post to the
"login_handler_path" of the plugin (optimally with a "came_from"
value to tell the plugin where to redirect the response to if the
authentication works properly). The "logout_handler_path" of this
plugin can be visited to perform a logout. The "came_from" value
also works there.

- Identifier plugins are now permitted to set a key in the environment
named 'repoze.who.application' on ingress (in 'identify'). If an
identifier plugin does so, this application is used instead of the
"normal" downstream application. This feature was added to more
simply support the redirecting form identifier plugin.

0.7

----------------

- Change the IMetadataProvider interface: this interface used to have
a "metadata" method which returned a dictionary. This method is not
part of that API anymore. It's been replaced with an "add_metadata"
method which has the signature::

def add_metadata(environ, identity):
"""
Add metadata to the identity (which is a dictionary)
"""

The return value is ignored. IMetadataProvider plugins are now
assumed to be responsible for 'scribbling' directly on the identity
that is passed in (it's a dictionary). The user id can always be
retrieved from the identity via identity['repoze.who.userid'] for
metadata plugins that rely on that value.

Page 6 of 7

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.