A Django middleware to authenticate users with Appwrite.
MIT License
Bot releases are hidden (Show)
PROJECT_API_KEY
: We have deprecated the use of PROJECT_API_KEY
in favor of improved security practices. The package will continue to function with PROJECT_API_KEY
set for backward compatibility, but a warning will be issued. It is recommended to remove this key at your earliest convenience. The warning message for PROJECT_API_KEY
usage will be removed in upcoming versions.PROJECT_API_KEY
; however, we encourage users to remove it as it will be phased out in future versions.PROJECT_API_KEY
.Published by khashashin about 1 year ago
For those using AppwriteMiddleware
, remember that CSRF protection is in place by default in Django. Since the middleware leverages session-based authentication, ensure that the CSRF tokens are correctly set and verified in AJAX requests to avoid 403 errors.
Published by khashashin about 1 year ago
For those using AppwriteMiddleware
, remember that CSRF protection is in place by default in Django. Since the middleware leverages session-based authentication, ensure that the CSRF tokens are correctly set and verified in AJAX requests to avoid 403 errors.
Published by khashashin about 1 year ago
AppwriteAuthentication
class, enabling Django Rest Framework users to authenticate with Appwrite easily. This authentication class leverages Appwrite's JWT mechanism to authenticate users, making it more streamlined and efficient.setup.py
Commands: Added custom build and publish commands in setup.py
, simplifying the package build and publish process. Users can now build the package using python setup.py build
and publish it with python setup.py publish --version=x.x.x
.AppwriteMiddleware
to fetch configurations more elegantly, avoiding redundancy. Also, improved error handling and logging mechanisms to provide clearer feedback to developers.AppwriteAuthentication
class, and updated usage examples.For those using AppwriteMiddleware
, remember that CSRF protection is in place by default in Django. Since the middleware leverages session-based authentication, ensure that the CSRF tokens are correctly set and verified in AJAX requests to avoid 403 errors.
Published by khashashin over 1 year ago
Configuration
Logging
Middleware
Header
Published by khashashin over 1 year ago
Published by khashashin over 1 year ago
Security: To improve the security of our system, replaced the user ID with JSON Web Tokens (JWT) in communication with the Appwrite server. This change prevents potential risk of attempting to login by generating random IDs.
Integration: Updated the documentation to include information and examples on using JWT in the frontend. This will help to integrate the application with the Appwrite server more easily and securely.
Published by khashashin over 1 year ago
User Verification: Added Django settings for email/phone verification. You can now enable or disable email or phone verification in the Django settings.
CI/CD: To make the release process smoother, added a GitHub Action for PyPI publication. This will allow to publish new releases directly from your GitHub repository to PyPI.
User Verification: Updated the documentation to include the new email/phone verification settings.
Published by khashashin over 1 year ago
Published by khashashin over 1 year ago
Published by khashashin over 1 year ago
The first release version 1.0.0 of the django-appwrite package is a middleware for Django that provides authentication for Appwrite users. The package enables Django to receive Appwrite authentication headers from client requests and process them to log in the corresponding user. The package implements an authentication backend that uses the Appwrite API to verify the authenticity of the provided headers. Additionally, the package includes a set of unit tests to ensure the functionality of the middleware and the backend. With this first version, Django developers can easily add Appwrite authentication to their projects and provide a seamless login experience for their Appwrite users.