registration¶
Subpackages¶
Submodules¶
jwt_allauth.registration.app_settings module¶
jwt_allauth.registration.serializers module¶
- class jwt_allauth.registration.serializers.RegisterSerializer(*args, **kwargs)[source]¶
Bases:
Serializer
- class jwt_allauth.registration.serializers.UserRegisterSerializer(*args, **kwargs)[source]¶
Bases:
RegisterSerializerRegistration serializer for admin-managed user creation. - Requires email and role. - Does not accept passwords; user sets password after email verification. - first_name/last_name optional.
- password1 = None¶
- password2 = None¶
jwt_allauth.registration.views module¶
- class jwt_allauth.registration.views.RegisterView(**kwargs)[source]¶
Bases:
CreateAPIView- create(request, *args, **kwargs)¶
- dispatch(*args, **kwargs)[source]¶
.dispatch() is pretty much the same as Django’s regular dispatch, but with extra hooks for startup, finalize, and exception handling.
- jwt_token¶
alias of
RefreshToken
- permission_classes = (<class 'rest_framework.permissions.AllowAny'>,)¶
- serializer_class¶
alias of
RegisterSerializer
- token_model¶
alias of
Token
- class jwt_allauth.registration.views.UserRegisterView(**kwargs)[source]¶
Bases:
CreateAPIViewAdmin-managed registration endpoint. - Only accessible to users with admin role (see AdminPermission). - Does not issue tokens on creation. - Triggers email verification; user will set password after verifying.
- create(request, *args, **kwargs)¶
- dispatch(*args, **kwargs)[source]¶
.dispatch() is pretty much the same as Django’s regular dispatch, but with extra hooks for startup, finalize, and exception handling.
- http_method_names = ['post', 'head', 'options']¶
- permission_classes = (<class 'jwt_allauth.permissions.RegisterUsersPermission'>,)¶
- serializer_class¶
alias of
UserRegisterSerializer