Creating a custom user in Django-restful framework and authenticating them using Simple JWT.

“Django-Restful Custom User Authentication Using Simple JWT”.png

Django_PostmanClip.tar.gz

initial-setup

installations

custom-model

reg-serializer

reg-view

reg-endpoint-one

reg-endpoint-two

reg-endpoint-three

email-verification-one

email-verification-two

resend-email-verification-one

resend-email-verification-two

login-serializer

login-view

login-view-one

login-endpoint-one

login-endpoint-two

password-reset-serializer

password-reset-email

password-reset-view

password-reset-endpoint-one

password-reset-endpoint-two

user-listing-and-retrieval-one

user-listing-and-retrieval-two

user-logout-and-token-blacklisting-one

user-logout-and-token-blacklisting-two

endpoint-listing-one

endpoint-listing-two

Postman-1

Django-Postman V 1.0-copy

In this course, you will learn to use a package called Simple JWT to help implement JWT authentication in your Django RESTful projects.

In the beginning, you will learn how to create custom users in Django using Django RESTful. Next, you will learn to register users using JWT and send them account verification emails. After that, you will learn how to make custom token claims when logging in users, and also how to refresh the tokens after expiry. You will then learn how to reset passwords and understand how password reset emails work. You will learn to organize your users in Django RESTful, log them out, and also black-list their JWT tokens. You will finish by learning how to manage and test your endpoints by documenting and testing them.

After the completion of this course, you will be able to create custom users in Django RESTful framework, authenticate them using Simple JWT, programmatically send account verification and password reset emails.

Custom User Authentication with Simple JWT in Django RESTful

Which method do we use to verify user login credentials in the login serializer?

Which method do we use to verify user login credentials in the login serializer?

The serializer provides the token field; therefore, the user is not responsible for filling it.

To prevent the user from tampering with the provided tokens

**(Select all that apply.)** Why is the `token` field in the login serializer a `read_only` field?

(Select all that apply.) Why is the <code>token</code> field in the login serializer a <code>read_only</code> field?

It takes them back to the registration endpoint.

It raises an `AuthenticationFailed` exception.

How does the login serializer respond if a user tries to log in with the wrong credentials?

How does the login serializer respond if a user tries to log in with the wrong credentials?

About This Course

Registering Custom User Using Simple JWT

Logging in User Using Simple JWT

Resetting User Password

Organizing Users

User Logout

Managing and Testing the Endpoints

Conclusion

Appendix

Quiz: User Login