Home/ Questions/Q 8621679
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-12T06:52:22+00:00

I’m setting up a Flask app with the flask-login extension. The flask-login documentation recommends

  • 0

I’m setting up a Flask app with the flask-login extension. The flask-login documentation recommends setting up an alternative token generator that does not simply use the user ID and app secret to create the session token (which is the default method). But it doesn’t provide any clear recommendations for how to do this.

So, for User.get_auth_token(), I’m using the make_secure_token function with the user email and password as parameters (so I get a hash of these parameters + app secret).

Next, I need to be able to get the user from the token with the token_loader callback. The default method for generating tokens in flask-login is to include both the raw user ID and a hash of the user ID + app secret. That makes finding the user from the token pretty simple – just grab the ID and look up the user.

But should I be exposing the user ID in the session token at all? If I don’t, should I store the session token in the database or somewhere else with the user ID to make a lookup possible?

In short: does anyone know what the best practice is for creating a secure token & corresponding token_loader callback?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    On the Flask mailing list, Matt Wright pointed me to his implementation in the flask-security extension. He uses itsdangerous to create a signed token which encodes a serialized (via URLSafeTimedSerializer()) list consisting of the user ID and the password hash. The token can then be decoded to grab the user ID.

    • 0