Add AuthToken Support and Device ID/Type to DRFPasswordless #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces the following changes to the DRFPasswordless repository:
AuthToken Support: Integrated the AuthToken app from the Django Rest Framework (DRF) into DRFPasswordless to enable token-based authentication for passwordless login. This will allow the app to issue and manage tokens for authenticated sessions.
Device Information:
Added support for device ID and device type fields to enhance user authentication and security.
The device ID is a 64-character unique identifier to distinguish user devices.
The device type field records the type of device (e.g., mobile, tablet, etc.) being used, providing better context for authentication events.
These changes are aimed at improving the security and usability of DRFPasswordless, enabling token-based authentication while supporting multi-device management.
Key Changes:
Integrated AuthToken app for token support.
Added new fields:
device_id (64-character unique identifier).
device_type (specifies the type of device).
Updated necessary views and serializers to handle the new fields and token support.
This enhancement will make the DRFPasswordless library more versatile, especially for apps that rely on token-based authentication systems and device tracking. Please review the changes and suggest any improvements.