Django-tequila

Latest version: v3.4.0

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

Scan your dependencies

Page 2 of 8

3.0.0

Added
- A test framework trough docker
- Add allowedrequesthosts parameter

Change
- Compatible with Django 2.1. Meaning we will suport only django 1.11 and 2.1
- Update the sample_app to reflect this evolution

Fix
- Sample_app work with SSL
- Fix field mapping for user, as some field where too small. Be warned, you may need to migrate your DB to reflect the change (see https://github.com/epfl-idevelop/django-tequila/commit/1f2f8af0bcd81c6dbd8d9a2385fbc17174f34ba3).
- Fix pip installation encoding failure

2.1.18

Fix
- Django authentication backend may not return any user
- Security fix : Force redirect url to have a slash

2.1.17

Fix
- Bump version for Pypi

2.1.16

Added
- Allow to get a different attribute for username value

Changed
- Use get_user_model to get the User (thanks llann)
- Remove LICENSE file, as 2.1.8 added copyright in source. The license should be more permissive now.
- Removing the 2.1.10 change that allow the force https redirect, as Tequila will do it by default.

Fixed
- Security fix : Disallow a redirect to a different site than the origin
- Django 1.11.x and python 3 compatibilities
- Some PEP8 formatting for *.py files

2.1.15

Fixed
- Check if user.is\_active==True before allowing user to connect

2.1.14

Fixed
- Accidently removing other parameters in url than the ask one, like 'key'

Page 2 of 8

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.