login, logout และวิวการยืนยันตัวตน

Verifying a user is only step one. To keep them logged in across requests, you start a session with Django's login helper. 🔑

login() takes the request and an authenticated user, then saves their id in the session. Future requests now know who they are.

After authenticate() succeeds, call login(request, user). From that point on, request.user is the signed-in person, not a guest.

To end a session, call logout(request). It clears the stored user id and any session data tied to that visit. 👋

Once logged in, request.user is available in every view. Check user.is_authenticated to tell members apart from anonymous visitors.

Django ships ready-made auth views so you do not hand-write login pages. They handle the form, validation, and session for you.

Include django.contrib.auth.urls to get login, logout, and password routes instantly under a path you choose.

The built-in LoginView renders a form and logs the user in on success. You mainly supply a template named registration/login.html.

LoginView passes a form variable to your template. Just render that form inside a POST and Django handles the rest.

Set LOGIN_REDIRECT_URL in settings to control where users land after a successful login, such as a dashboard.

The matching LogoutView ends the session, and LOGOUT_REDIRECT_URL decides where signed-out users are sent next.

Which function actually starts a logged-in session?

You used login() and logout() to manage sessions, and wired Django's auth views and redirect settings to avoid boilerplate. ✅