Django-azure-auth

Latest version: v2.1.0

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

Scan your dependencies

Page 1 of 2

2.1.0

Added

- Add optional setting for Graph API `/me` URL.

2.0.2

Fixed

- Validates that the `next` path is a relative path to only allow redirects within the host domain.

2.0.1

Fixed

- Auth handler correctly removes users from Django groups when the ID token `roles` claim is empty.

2.0.0

Fixed

- Auth handler no longer assumes the user model includes `first_name` and `last_name` fields ([23](https://github.com/Weird-Sheep-Labs/django-azure-auth/issues/23)). This introduces a breaking change as these fields are no longer populated on the model by default.

Changed

- Optional AAD attributes to be retrieved can be specified in the settings ([11](https://github.com/Weird-Sheep-Labs/django-azure-auth/issues/11)).
- AAD attributes and ID token claims can be mapped to Django User model fields using a user-defined function ([23](https://github.com/Weird-Sheep-Labs/django-azure-auth/issues/23)).

1.4.3

Fixed

- Fixed login callback redirect bug caused by AAD `state` parameter being populated by Azure AD when empty ([30](https://github.com/Weird-Sheep-Labs/django-azure-auth/issues/30)).

1.4.2

Changed

- Change post-login redirect mechanism to use the AAD `state` parameter rather than the Django user session (28).
- Include the redirect functionality for decorator-protected views, not just middleware-protected views (28).

Page 1 of 2

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.