2018-01-02T17:20:33Z

The Flask Mega-Tutorial Part V: User Logins

This is the fifth installment of the Flask Mega-Tutorial series, in which I'm going to tell you how to create a user login subsystem.

For your reference, below is a list of the articles in this series.

In Chapter 3 you learned how to create the user login form, and in Chapter 4 you learned how to work with a database. This chapter will teach you how to combine the topics from those two chapters to create a simple user login system.

The GitHub links for this chapter are: Browse, Zip, Diff.

Password Hashing

In Chapter 4 the user model was given a password_hash field, that so far is unused. The purpose of this field is to hold a hash of the user password, which will be used to verify the password entered by the user during the log in process. Password hashing is a complicated topic that should be left to security experts, but there are several easy to use libraries that implement all that logic in a way that is simple to be invoked from an application.

One of the packages that implement password hashing is Werkzeug, which you may have seen referenced in the output of pip when you install Flask, since it is one of its core dependencies. Since it is a dependency, Werkzeug is already installed in your virtual environment. The following Python shell session demonstrates how to hash a password:

>>> from werkzeug.security import generate_password_hash
>>> hash = generate_password_hash('foobar')
>>> hash
'pbkdf2:sha256:50000$vT9fkZM8$04dfa35c6476acf7e788a1b5b3c35e217c78dc04539d295f011f01f18cd2'

In this example, the password foobar is transformed into a long encoded string through a series of cryptographic operations that have no known reverse operation, which means that a person that obtains the hashed password will be unable to use it to obtain the original password. As an additional measure, if you hash the same password multiple times, you will get different results, so this makes it impossible to identify if two users have the same password by looking at their hashes.

The verification process is done with a second function from Werkzeug, as follows:

>>> from werkzeug.security import check_password_hash
>>> check_password_hash(hash, 'foobar')
True
>>> check_password_hash(hash, 'barfoo')
False

The verification function takes a password hash that was previously generated, and a password entered by the user at the time of log in. The function returns True if the password provided by the user matches the hash, or False otherwise.

The whole password hashing logic can be implemented as two new methods in the user model:

app/models.py: Password hashing and verification

from werkzeug.security import generate_password_hash, check_password_hash

# ...

class User(db.Model):
    # ...

    def set_password(self, password):
        self.password_hash = generate_password_hash(password)

    def check_password(self, password):
        return check_password_hash(self.password_hash, password)

With these two methods in place, a user object is now able to do secure password verification, without the need to ever store original passwords. Here is an example usage of these new methods:

>>> u = User(username='susan', email='susan@example.com')
>>> u.set_password('mypassword')
>>> u.check_password('anotherpassword')
False
>>> u.check_password('mypassword')
True

Introduction to Flask-Login

In this chapter I'm going to introduce you to a very popular Flask extension called Flask-Login. This extension manages the user logged-in state, so that for example users can log in to the application and then navigate to different pages while the application "remembers" that the user is logged in. It also provides the "remember me" functionality that allows users to remain logged in even after closing the browser window. To be ready for this chapter, you can start by installing Flask-Login in your virtual environment:

(venv) $ pip install flask-login

As with other extensions, Flask-Login needs to be created and initialized right after the application instance in app/__init__.py. This is how this extension is initialized:

app/__init__.py: Flask-Login initialization

# ...
from flask_login import LoginManager

app = Flask(__name__)
# ...
login = LoginManager(app)

# ...

Preparing The User Model for Flask-Login

The Flask-Login extension works with the application's user model, and expects certain properties and methods to be implemented in it. This approach is nice, because as long as these required items are added to the model, Flask-Login does not have any other requirements, so for example, it can work with user models that are based on any database system.

The four required items are listed below:

  • is_authenticated: a property that is True if the user has valid credentials or False otherwise.
  • is_active: a property that is True if the user's account is active or False otherwise.
  • is_anonymous: a property that is False for regular users, and True for a special, anonymous user.
  • get_id(): a method that returns a unique identifier for the user as a string (unicode, if using Python 2).

I can implement these four easily, but since the implementations are fairly generic, Flask-Login provides a mixin class called UserMixin that includes generic implementations that are appropriate for most user model classes. Here is how the mixin class is added to the model:

app/models.py: Flask-Login user mixin class

# ...
from flask_login import UserMixin

class User(UserMixin, db.Model):
    # ...

User Loader Function

Flask-Login keeps track of the logged in user by storing its unique identifier in Flask's user session, a storage space assigned to each user who connects to the application. Each time the logged-in user navigates to a new page, Flask-Login retrieves the ID of the user from the session, and then loads that user into memory.

Because Flask-Login knows nothing about databases, it needs the application's help in loading a user. For that reason, the extension expects that the application will configure a user loader function, that can be called to load a user given the ID. This function can be added in the app/models.py module:

app/models.py: Flask-Login user loader function

from app import login
# ...

@login.user_loader
def load_user(id):
    return User.query.get(int(id))

The user loader is registered with Flask-Login with the @login.user_loader decorator. The id that Flask-Login passes to the function as an argument is going to be a string, so databases that use numeric IDs need to convert the string to integer as you see above.

Logging Users In

Let's revisit the login view function, which as you recall, implemented a fake login that just issued a flash() message. Now that the application has access to a user database and knows how to generate and verify password hashes, this view function can be completed.

app/routes.py: Login view function logic

# ...
from flask_login import current_user, login_user
from app.models import User

# ...

@app.route('/login', methods=['GET', 'POST'])
def login():
    if current_user.is_authenticated:
        return redirect(url_for('index'))
    form = LoginForm()
    if form.validate_on_submit():
        user = User.query.filter_by(username=form.username.data).first()
        if user is None or not user.check_password(form.password.data):
            flash('Invalid username or password')
            return redirect(url_for('login'))
        login_user(user, remember=form.remember_me.data)
        return redirect(url_for('index'))
    return render_template('login.html', title='Sign In', form=form)

The top two lines in the login() function deal with a weird situation. Imagine you have a user that is logged in, and the user navigates to the /login URL of your application. Clearly that is a mistake, so I want to not allow that. The current_user variable comes from Flask-Login and can be used at any time during the handling to obtain the user object that represents the client of the request. The value of this variable can be a user object from the database (which Flask-Login reads through the user loader callback I provided above), or a special anonymous user object if the user did not log in yet. Remember those properties that Flask-Login required in the user object? One of those was is_authenticated, which comes in handy to check if the user is logged in or not. When the user is already logged in, I just redirect to the index page.

In place of the flash() call that I used earlier, now I can log the user in for real. The first step is to load the user from the database. The username came with the form submission, so I can query the database with that to find the user. For this purpose I'm using the filter_by() method of the SQLAlchemy query object. The result of filter_by() is a query that only includes the objects that have a matching username. Since I know there is only going to be one or zero results, I complete the query by calling first(), which will return the user object if it exists, or None if it does not. In Chapter 4 you have seen that when you call the all() method in a query, the query executes and you get a list of all the results that match that query. The first() method is another commonly used way to execute a query, when you only need to have one result.

If I got a match for the username that was provided, I can next check if the password that also came with the form is valid. This is done by invoking the check_password() method I defined above. This will take the password hash stored with the user and determine if the password entered in the form matches the hash or not. So now I have two possible error conditions: the username can be invalid, or the password can be incorrect for the user. In either of those cases, I flash an message, and redirect back to the login prompt so that the user can try again.

If the username and password are both correct, then I call the login_user() function, which comes from Flask-Login. This function will register the user as logged in, so that means that any future pages the user navigates to will have the current_user variable set to that user.

To complete the login process, I just redirect the newly logged-in user to the index page.

Logging Users Out

I know I will also need to offer users the option to log out of the application. This can be done with Flask-Login's logout_user() function. Here is the logout view function:

app/routes.py: Logout view function

# ...
from flask_login import logout_user

# ...

@app.route('/logout')
def logout():
    logout_user()
    return redirect(url_for('index'))

To expose this link to users, I can make the Login link in the navigation bar automatically switch to a Logout link after the user logs in. This can be done with a conditional in the base.html template:

app/templates/base.html: Conditional login and logout links

    <div>
        Microblog:
        <a href="{{ url_for('index') }}">Home</a>
        {% if current_user.is_anonymous %}
        <a href="{{ url_for('login') }}">Login</a>
        {% else %}
        <a href="{{ url_for('logout') }}">Logout</a>
        {% endif %}
    </div>

The is_anonymous property is one of the attributes that Flask-Login adds to user objects through the UserMixin class. The current_user.is_anonymous expression is going to be True only when the user is not logged in.

Requiring Users To Login

Flask-Login provides a very useful feature that forces users to log in before they can view certain pages of the application. If a user who is not logged in tries to view a protected page, Flask-Login will automatically redirect the user to the login form, and only redirect back to the page the user wanted to view after the login process is complete.

For this feature to be implemented, Flask-Login needs to know what is the view function that handles logins. This can be added in app/__init__.py:

# ...
login = LoginManager(app)
login.login_view = 'login'

The 'login' value above is the function (or endpoint) name for the login view. In other words, the name you would use in a url_for() call to get the URL.

The way Flask-Login protects a view function against anonymous users is with a decorator called @login_required. When you add this decorator to a view function below the @app.route decorators from Flask, the function becomes protected and will not allow access to users that are not authenticated. Here is how the decorator can be applied to the index view function of the application:

app/routes.py: @login\_required decorator

from flask_login import login_required

@app.route('/')
@app.route('/index')
@login_required
def index():
    # ...

What remains is to implement the redirect back from the successful login to the page the user wanted to access. When a user that is not logged in accesses a view function protected with the @login_required decorator, the decorator is going to redirect to the login page, but it is going to include some extra information in this redirect so that the application can then return to the first page. If the user navigates to /index, for example, the @login_required decorator will intercept the request and respond with a redirect to /login, but it will add a query string argument to this URL, making the complete redirect URL /login?next=/index. The next query string argument is set to the original URL, so the application can use that to redirect back after login.

Here is a snippet of code that shows how to read and process the next query string argument:

app/routes.py: Redirect to "next" page

from flask import request
from werkzeug.urls import url_parse

@app.route('/login', methods=['GET', 'POST'])
def login():
    # ...
    if form.validate_on_submit():
        user = User.query.filter_by(username=form.username.data).first()
        if user is None or not user.check_password(form.password.data):
            flash('Invalid username or password')
            return redirect(url_for('login'))
        login_user(user, remember=form.remember_me.data)
        next_page = request.args.get('next')
        if not next_page or url_parse(next_page).netloc != '':
            next_page = url_for('index')
        return redirect(next_page)
    # ...

Right after the user is logged in by calling Flask-Login's login_user() function, the value of the next query string argument is obtained. Flask provides a request variable that contains all the information that the client sent with the request. In particular, the request.args attribute exposes the contents of the query string in a friendly dictionary format. There are actually three possible cases that need to be considered to determine where to redirect after a successful login:

  • If the login URL does not have a next argument, then the user is redirected to the index page.
  • If the login URL includes a next argument that is set to a relative path (or in other words, a URL without the domain portion), then the user is redirected to that URL.
  • If the login URL includes a next argument that is set to a full URL that includes a domain name, then the user is redirected to the index page.

The first and second cases are self-explanatory. The third case is in place to make the application more secure. An attacker could insert a URL to a malicious site in the next argument, so the application only redirects when the URL is relative, which ensures that the redirect stays within the same site as the application. To determine if the URL is relative or absolute, I parse it with Werkzeug's url_parse() function and then check if the netloc component is set or not.

Showing The Logged In User in Templates

Do you recall that way back in Chapter 2 I created a fake user to help me design the home page of the application before the user subsystem was in place? Well, the application has real users now, so I can now remove the fake user and start working with real users. Instead of the fake user I can use Flask-Login's current_user in the template:

app/templates/index.html: Pass current user to template

{% extends "base.html" %}

{% block content %}
    <h1>Hi, {{ current_user.username }}!</h1>
    {% for post in posts %}
    <div><p>{{ post.author.username }} says: <b>{{ post.body }}</b></p></div>
    {% endfor %}
{% endblock %}

And I can remove the user template argument in the view function:

app/routes.py: Do not pass user to template anymore

@app.route('/')
@app.route('/index')
@login_required
def index():
    # ...
    return render_template("index.html", title='Home Page', posts=posts)

This is a good time to test how the login and logout functionality works. Since there is still no user registration, the only way to add a user to the database is to do it via the Python shell, so run flask shell and enter the following commands to register a user:

>>> u = User(username='susan', email='susan@example.com')
>>> u.set_password('cat')
>>> db.session.add(u)
>>> db.session.commit()

If you start the application and go to the application's / or /index URLs, you will be immediately redirected to the login page, and after you log in using the credentials of the user that you added to your database, you will be returned to the original page, in which you will see a personalized greeting.

User Registration

The last piece of functionality that I'm going to build in this chapter is a registration form, so that users can register themselves through a web form. Let's begin by creating the web form class in app/forms.py:

app/forms.py: User registration form

from flask_wtf import FlaskForm
from wtforms import StringField, PasswordField, BooleanField, SubmitField
from wtforms.validators import ValidationError, DataRequired, Email, EqualTo
from app.models import User

# ...

class RegistrationForm(FlaskForm):
    username = StringField('Username', validators=[DataRequired()])
    email = StringField('Email', validators=[DataRequired(), Email()])
    password = PasswordField('Password', validators=[DataRequired()])
    password2 = PasswordField(
        'Repeat Password', validators=[DataRequired(), EqualTo('password')])
    submit = SubmitField('Register')

    def validate_username(self, username):
        user = User.query.filter_by(username=username.data).first()
        if user is not None:
            raise ValidationError('Please use a different username.')

    def validate_email(self, email):
        user = User.query.filter_by(email=email.data).first()
        if user is not None:
            raise ValidationError('Please use a different email address.')

There are a couple of interesting things in this new form related to validation. First, for the email field I've added a second validator after DataRequired, called Email. This is another stock validator that comes with WTForms that will ensure that what the user types in this field matches the structure of an email address.

The Email() validator from WTForms requires an external dependency to be installed:

(venv) $ pip install email-validator

Since this is a registration form, it is customary to ask the user to type the password two times to reduce the risk of a typo. For that reason I have password and password2 fields. The second password field uses yet another stock validator called EqualTo, which will make sure that its value is identical to the one for the first password field.

When you add any methods that match the pattern validate_<field_name>, WTForms takes those as custom validators and invokes them in addition to the stock validators. I have added two of those methods to this class for the username and email fields. In this case I want to make sure that the username and email address entered by the user are not already in the database, so these two methods issue database queries expecting there will be no results. In the event a result exists, a validation error is triggered by raising an exception of type ValidationError. The message included as the argument in the exception will be the message that will be displayed next to the field for the user to see.

To display this form on a web page, I need to have an HTML template, which I'm going to store in file app/templates/register.html. This template is constructed similarly to the one for the login form:

app/templates/register.html: Registration template

{% extends "base.html" %}

{% block content %}
    <h1>Register</h1>
    <form action="" method="post">
        {{ form.hidden_tag() }}
        <p>
            {{ form.username.label }}<br>
            {{ form.username(size=32) }}<br>
            {% for error in form.username.errors %}
            <span style="color: red;">[{{ error }}]</span>
            {% endfor %}
        </p>
        <p>
            {{ form.email.label }}<br>
            {{ form.email(size=64) }}<br>
            {% for error in form.email.errors %}
            <span style="color: red;">[{{ error }}]</span>
            {% endfor %}
        </p>
        <p>
            {{ form.password.label }}<br>
            {{ form.password(size=32) }}<br>
            {% for error in form.password.errors %}
            <span style="color: red;">[{{ error }}]</span>
            {% endfor %}
        </p>
        <p>
            {{ form.password2.label }}<br>
            {{ form.password2(size=32) }}<br>
            {% for error in form.password2.errors %}
            <span style="color: red;">[{{ error }}]</span>
            {% endfor %}
        </p>
        <p>{{ form.submit() }}</p>
    </form>
{% endblock %}

The login form template needs a link that sends new users to the registration form, right below the form:

app/templates/login.html: Link to registration page

    <p>New User? <a href="{{ url_for('register') }}">Click to Register!</a></p>

And finally, I need to write the view function that is going to handle user registrations in app/routes.py:

app/routes.py: User registration view function

from app import db
from app.forms import RegistrationForm

# ...

@app.route('/register', methods=['GET', 'POST'])
def register():
    if current_user.is_authenticated:
        return redirect(url_for('index'))
    form = RegistrationForm()
    if form.validate_on_submit():
        user = User(username=form.username.data, email=form.email.data)
        user.set_password(form.password.data)
        db.session.add(user)
        db.session.commit()
        flash('Congratulations, you are now a registered user!')
        return redirect(url_for('login'))
    return render_template('register.html', title='Register', form=form)

And this view function should also be mostly self-explanatory. I first make sure the user that invokes this route is not logged in. The form is handled in the same way as the one for logging in. The logic that is done inside the if validate_on_submit() conditional creates a new user with the username, email and password provided, writes it to the database, and then redirects to the login prompt so that the user can log in.

Registration Form

With these changes, users should be able to create accounts on this application, and log in and out. Make sure you try all the validation features I've added in the registration form to better understand how they work. I am going to revisit the user authentication subsystem in a future chapter to add additional functionality such as to allow the user to reset the password if forgotten. But for now, this is enough to continue building other areas of the application.

578 comments

  • #201 Miguel Grinberg said 2018-10-02T21:59:22Z

    @Igor: your validate_username() method is missing an argument. Maybe you forgot to add self as first argument?

  • #202 Miguel Grinberg said 2018-10-02T22:00:46Z

    @Gabriel: the algorithms are different, but both have the goal of creating impossibly difficult to hack password hashes.

  • #203 AR said 2018-10-17T17:59:40Z

    Hi Miguel,

    Under the profile settings, I have provided an option to change password for logged in users. Its the account-settings page. (www.domain.com/account-settings). Once the user fill the form, password is updated after necessary checks, and the user is taken back to the same page (www.domain.com/account-settings) with an status update about password change.

    From here, if a user visits any other page or click any link on same page, I want to log him out and redirect to login page. Logout route takes care of logging out. Challenge is how to redirect to logout route when the user attempts to visit any other page from the /account-settings page right after changing the password?

    I can think of creating a flag / column in db and set / reset it and check on each page load but it seems to be consuming unnecessary processing.

    Gmail has similar functionality.

  • #204 Miguel Grinberg said 2018-10-17T18:31:02Z

    @AR: Just call logout_user() in the password change route.

  • #205 AR said 2018-10-18T03:10:08Z

    If Logout route is called during password change then user will be logged out as soon as password is changed. What essentially I want is to take user back to the settings page, flash 'password changed successfully' and then if the user click any link from Settings page, log him out. But the control must return to settings page after password update. Settings page is @login_required page.

  • #206 Miguel Grinberg said 2018-10-18T14:17:18Z

    @AR: my answer does not change. The change password route should log the user out, then return the settings page template, with the user logged out. The moment the user clicks on any link, they'll have to log in again.

  • #207 Grace said 2018-10-22T07:23:47Z

    Hello Miguel

    I found that the current_user.is_authenticated is a method, not a boolean value, I try to run your code, but the page always redirect to index page no matter the user is authenticated or not. I have to call this method to make it work as expect.

    if current_user.is_authenticated(): return redirect(url_for('index'))

    I used Flask-Login Version: 0.2.1, Flask Version: 0.12.4

  • #208 Miguel Grinberg said 2018-10-23T17:54:08Z

    @Grace: version 0.2.x of Flask-Login is a few years old, things were different back then. I recommend you upgrade instead of adapting the code to such an old version.

  • #209 chengi said 2018-10-27T22:06:20Z

    Hi, I cloned your repo for this chapter. I keep getting this error: 127.0.0.1 - - [27/Oct/2018 18:04:54] "GET / HTTP/1.1" 302 - 127.0.0.1 - - [27/Oct/2018 18:04:54] "GET /login?next=%2F HTTP/1.1" 302 - 127.0.0.1 - - [27/Oct/2018 18:04:54] "GET /index HTTP/1.1" 302 - 127.0.0.1 - - [27/Oct/2018 18:04:54] "GET /login?next=%2Findex HTTP/1.1" 302 - 127.0.0.1 - - [27/Oct/2018 18:04:54] "GET /index HTTP/1.1" 302 - 127.0.0.1 - - [27/Oct/2018 18:04:54] "GET /login?next=%2Findex HTTP/1.1" 302 - 127.0.0.1 - - [27/Oct/2018 18:04:54] "GET /index HTTP/1.1" 302 - 127.0.0.1 - - [27/Oct/2018 18:04:54] "GET /login?next=%2Findex HTTP/1.1" 302 - 127.0.0.1 - - [27/Oct/2018 18:04:54] "GET /index HTTP/1.1" 302 - 127.0.0.1 - - [27/Oct/2018 18:04:54] "GET /login?next=%2Findex HTTP/1.1" 302 - 127.0.0.1 - - [27/Oct/2018 18:04:54] "GET /index HTTP/1.1" 302 - 127.0.0.1 - - [27/Oct/2018 18:04:54] "GET /login?next=%2Findex HTTP/1.1" 302 - 127.0.0.1 - - [27/Oct/2018 18:04:54] "GET /index HTTP/1.1" 302 - 127.0.0.1 - - [27/Oct/2018 18:04:54] "GET /login?next=%2Findex HTTP/1.1" 302 - 127.0.0.1 - - [27/Oct/2018 18:04:54] "GET /index HTTP/1.1" 302 - 127.0.0.1 - - [27/Oct/2018 18:04:54] "GET /login?next=%2Findex HTTP/1.1" 302 - 127.0.0.1 - - [27/Oct/2018 18:04:54] "GET /index HTTP/1.1" 302 - 127.0.0.1 - - [27/Oct/2018 18:04:54] "GET /login?next=%2Findex HTTP/1.1" 302 - 127.0.0.1 - - [27/Oct/2018 18:04:54] "GET /index HTTP/1.1" 302 - 127.0.0.1 - - [27/Oct/2018 18:04:54] "GET /login?next=%2Findex HTTP/1.1" 302 -

    And then in browser I get This page isn’t working localhost redirected you too many times.

  • #210 chengi said 2018-10-27T22:22:21Z

    I think you have a bug.. if current_user.is_authenticated should be if current_user.is_authenticated()

  • #211 Miguel Grinberg said 2018-10-27T22:47:48Z

    @chengi: No. You are using a very old version of Flask-Login. Upgrade and you will be fine.

  • #212 Dheeraj M Pai said 2018-11-07T18:06:35Z

    Do I get the complete code anywhere?

  • #213 Miguel Grinberg said 2018-11-07T22:39:20Z

    @Dheeraj: at the beginning of each chapter there is a download link.

  • #214 Stephanie said 2018-11-18T18:59:09Z

    The def index(): return render_template("index.html", title='Home Page', posts=posts) returns an error: NameError: name 'posts' is not defined

    I removed the posts to get it to render the index. Did I miss something in the earlier tutorial? I've gone back through everything, but it all seems correct.

    Thx for any info!

  • #215 György Kovács said 2018-11-19T20:04:17Z

    Hi Miguel, thanks for the great tutorial! One particular question I have in mind about this one. Clearly, the login function works. However, I find strange the following one: when the login function is called with the GET method, a LoginForm is instantiated, used to render the template, etc. Then, when the login function is called with the POST method, another LoginForm object is instantiated, which has never been rendered yet, still, one can query the form.request.username field, even though it seems to be a brand new object. What is going on in the background? Thanks a lot in advance!

  • #216 Miguel Grinberg said 2018-11-20T10:01:56Z

    @Stephanie: Did you define the "posts" variable above the return statement? See this link: https://github.com/miguelgrinberg/microblog/blob/v0.5/app/routes.py#L13-L22

  • #217 Miguel Grinberg said 2018-11-20T10:11:11Z

    @György: The login form object uses information about the request provided by Flask to initialize itself. When the client sent a GET request, the form object initializes as an empty form, since there is no form data available. When the client sends a POST request with form data, all that data is loaded into the form object, and you can access these field values.

  • #218 Danko said 2018-11-20T13:01:14Z

    Why do we make validations (in the registration form) of the form entries in the forms.py file: def validate_username(self, username): user = User.query.filter_by(username=username.data).first() if user is not None: raise ValidationError('Please use a different username.')

    def validate_email(self, email): user = User.query.filter_by(email=email.data).first() if user is not None: raise ValidationError('Please use a different email address.')

    and not in routes like for the login form:

    if user is None or not user.check_password(form.password.data): flash('Invalid username or password')

  • #219 Miguel Grinberg said 2018-11-20T22:33:05Z

    @Danko: validations that you do in the form can display error messages that are specific to a field, and can appear next to the field when the form is rendered again to the user.

  • #220 Daniël Lacko said 2018-11-27T15:16:36Z

    Hi Miguel, and thanks a lot for this wonderful tutorial! I'm now going through it for the first time, and I noticed a minor problem: I could not get the register page to show the validation errors as in your final screenshot. Same thing when I used the code from the repository. I suspect you forgot to add a novalidate attribute to the form tag in the register.html template, so

    <form action="" method="post">

    should be:

    <form action="" method="post" novalidate>

    After adding this attribute (as on the login.html page) the browser no longer takes over the validation and everything works as expected.

  • #221 Newbie said 2018-11-30T07:56:55Z

    Miguel, Have a generic question. After login required condition is true, means user is authenticated, What is the ideal way to prevent authenticated users from accessing other users' data by typing in urls in the browser.

    Suppose we have an endpoint /users//edit and we have login required decorator.

    What stops a user with id 101 from editing data of user 102 by typing /users/102/edit in browser after logging in?

  • #222 Miguel Grinberg said 2018-11-30T09:19:28Z

    @Newbie: this is covered later in the tutorial, at this point there is nothing to edit. Your application has to check for those conditions and only allow requests to complete when the authenticated user satisfies the conditions for the request.

  • #223 Georgi Stoyanov said 2018-12-04T16:04:57Z

    I want to have a login form without registration form, and to use a master username and a password for accessing the site. How can I do that? I have created a User model in the database containing username and hashed password field.

  • #224 Miguel Grinberg said 2018-12-04T16:53:40Z

    @Georgi: Just don't have a registration route in your app, and that will prevent users from registering. When you want to register a user you need to add it to the database yourself.

  • #225 AR said 2018-12-05T11:32:58Z

    Hi Miguel,

    hash generated here is sha256. what should i do if i need sh512 with an additional custom salt?

Leave a Comment