Invenio-accounts

Latest version: v5.0.1

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

Scan your dependencies

Page 8 of 8

1.1.2

- Fixes requirements for Flask, Werkzeug and Flask-Login due to
incompatibilities of latest released modules.

1.1.1

- Fixes an issue where the HTTP headers X-Session-ID and X-User-ID are added
even if the value is not known. This causes 'None' to be logged in Nginx,
instead of simply '-'.

1.1.0

- Added support for for adding the user id and session id of the current user
into the HTTP headers (``X-User-ID`` and ``X-Session-ID``) for upstream
servers to use. For instance, this way current user/session ids can be logged
by Nginx into the web server access logs. The feature is off by default and
can be enabled via the ``ACCOUNTS_USERINFO_HEADERS`` configuration variable.
Note: The upstream server should strip the two headers from the response
returned to the client. The purpose is purely to allow upstream proxies like
Nginx to log the user/session id for a specific request.

- Changed token expiration from 5 days to 30 minutes for the password reset
token and email confirmation token. Using the tokens will as a side-effect
login in the user, which means that if the link is leaked (e.g. forwarded by
the users themselves), then another person can use the link to access the
account. Flask-Security v3.1.0 addresses this issue, but has not yet been
released.

- Fixes issue that could rehash the user password in the adminstration
interface.

1.0.2

- Added AnonymousIdentity loader to app initialisation to fix the ``any_user``
Need in Invenio-Access.

1.0.1

- Bumped Flask-CeleryExt from v0.3.0 to v0.3.1 to fix issue with Celery version
string not being parsable and thus causing problems with installing Celery.

1.0.0

- Initial public release.

Page 8 of 8

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.