Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Flask JWT Router is a Python library that adds authorised routes to a Flask app
Read the docs: Flask-JWT-Router
Flask JWT Router is a Python library that adds authorised routes to a Flask app. Both basic & Google's OAuth2.0 authentication is supported.
from flask_jwt_router import JwtRoutes
jwt_routes = JwtRoutes()
jwt_routes.init_app(
app,
entity_models=[MyModel],
)
Now your front end needs a token. Create an endpoint & return a new access token from the clients header code. For Example::
from flask import request
@app.routes("/login", methods=["POST"])
def login():
jwt_routes.google.oauth_login(request) # Pass in Flask's request
Now, the next time your front-end requests authorised resources flask-jwt-router will authenticate with this access token until it expires.
Stable version
pip install flask-jwt-router
from flask import Flask
from flask_jwt_router import JwtRoutes
app = Flask(__name__)
# You are required to always set a unique SECRET_KEY for your app
app.config["SECRET_KEY"] = "your_app_secret_key"
JwtRoutes(app)
# If you're using the Flask factory pattern:
jwt_routes = JwtRoutes() # Example with *entity_model - see below
def create_app(config):
...
jwt_routes.init_app(app)
app.config["WHITE_LIST_ROUTES"] = [
("POST", "/register"),
]
@app.route("/register", methods=["POST"])
def register():
return "I don't need authorizing!"
# All routes will
app.config["JWT_ROUTER_API_NAME"] = "/api/v1"
app.config["WHITE_LIST_ROUTES"] = [
("POST", "/register"),
]
@app.route("/api/v1/register", methods=["POST"])
def register():
return "I don't need authorizing!"
# Define homepage template routes for example on JWT_IGNORE_ROUTES
# & still get to use the api name on request handlers returning resources
app.config["IGNORED_ROUTES"] = [
("GET", "/")
]
# Create your entity model (example uses Flask-SqlAlchemy)
class UserModel(db.Model):
__tablename__ = "users"
id = db.Column(db.Integer, primary_key=True)
name = db.Column(db.String)
# You can define the primary key name with `ENTITY_KEY` on Flask's config
app.config["ENTITY_KEY"] = "user_id"
# (`id` is used by default)
JwtRoutes(app, entity_models=[UserModel, TeacherModel, ...etc])
# Or pass later with `init_app`
def create_app(config):
...
jwt_routes.init_app(app, entity_models=[UserModel, TeacherModel, ...etc])
from your_app import jwt_routes
# white list the routes
app.config["WHITE_LIST_ROUTES"] = [
("POST", "/register"),
("POST", "/login"),
]
@app.route("/login", methods=["POST"])
def register():
"""I'm registering a new user & returning a token!"""
return jsonify({
"token": jwt_routes.create_token(entity_id=1, table_name='users')
})
@app.route("/your_resource", methods=["POST"])
def login():
"""I'm authorized & updating my token!"""
return jsonify({
"token": jwt_routes.update_token(entity_id=1)
})
*Warning: The table_name
must be the same as your tablename or __tablename__
attribute's value.
(With SqlAlchemy, you can define a __tablename__
attribute directly or else
the name is derived from your entity’s database table name).
There are two ways to set the expire duration of the JWT.
from your app config
# Set the token expire duration to 7 days
app.config["JWT_EXPIRE_DAYS"] = 7
calling the set_exp
# Set the token expire duration to 14 days
jwt_routes = JwtRoutes()
# jwt_routes.init_app( ...etc
jwt_routes.set_exp(expire_days=14)
By default the expire duration is set to 30 days
Create a new entity & return a new token
@app.route("/register", methods=["POST"])
def register():
user_data = request.get_json()
try:
user = UserModel(**user_data)
user.create_user() # your entity creation logic
# Here we pass the id as a kwarg to `create_token`
token: str = jwt_routes.create_token(entity_id=user.id, table_name="users")
# Now we can return a new token!
return {
"message": "User successfully created.",
"token": str(token), # casting is optional
}, 200
Access entity on Flask's global context
from app import app, jwt_routes
# Example uses Marshmallow to serialize entity object
class EntitySchema(Schema):
id = fields.Integer()
name = fields.String()
@app.route("/login", methods=["GET"])
def login():
user_data = g.get("users") # This is your SqlAlchemy `__tablename__` or the default name.
try:
user_dumped = UserSchema().dump(user_data)
except ValidationError as _:
return {
"error": "User requested does not exist."
}, 401
return {
"data": user_dumped,
"token": jwt_routes.update_token(entity_id=user_data.id),
}, 200
If you are handling a request with a token in the headers you can call::
jwt_routes.update_token(entity_id=user_data.id)
If you are handling a request without a token in the headers you can call::
jwt_routes.create_token(entity_id=user_data.id, table_name="users")
An Example configuration for registering & logging in users of different types:
app.config["IGNORED_ROUTES"] = [("GET", "/")]
app.config["JWT_ROUTER_API_NAME"] = "/api/v1"
app.config["WHITE_LIST_ROUTES"] = [
("POST", "/auth/user"), ("POST", "/auth/user/login"),
("POST", "/auth/teacher"), ("POST", "/auth/teacher/login"),
]
# Optionally, you can pass your models to Flask's config:
app.config["ENTITY_MODELS"] = [ UserModel, TeacherModel, ...etc ]
To send the JSON web token from your front end, you will need to pass a Bearer
string in your authorization header.
For example:
fetch(url, {
headers: {
Authorization: "Bearer <my_token>",
}
})
If you require calling a resource without passing headers, then you can use the auth
query param (useful when streaming video files):
url = "http://example.com/cars?auth=my_token"
Read the detailed instructions here: Flask-JWT-Router
from flask_jwt_router import Google, JwtRoutes
oauth_options = {
"client_id": "<CLIENT_ID>",
"client_secret": "<CLIENT_SECRET>",
"redirect_uri": "http://localhost:3000",
"tablename": "users",
"email_field": "email",
"expires_in": 3600,
}
jwt_routes = JwtRoutes()
jwt_routes.init_app(
app,
google_oauth=oauth_options,
strategies=[Google],
entity_models=[MyModel],
)
Flask-JWT-Router supports auth Google's OAuth 2.0 Single Sign On strategy if you are using React only. (We will provide Google's OAuth 2.0 Single Sign On strategy for server to server as soon as possible!).
Create a login route for Google's OAuth 2.0
@app.route("/api/v1/google_login", methods=["POST"])
def google_login():
google = jwt_routes.get_strategy("Google")
data = google.oauth_login(request)
return data, 200
If your app requires multiple redirect uri's then
you can use the redirect_uri
kwarg to assign a uri for the current
request handler. For example:
google = jwt_routes.get_strategy("Google")
data = google.oauth_login(request, redirect="http://another_redirect.com")
We have created a ReactJS library specifically for Flask-JWT-Router - react-google-oauth2.0 In your React app directory install react-google-oauth2.0:
npm install react-google-oauth2 --save
Testing OAuth2.0 in a Flask app is non-trivial, especially if you rely on Flask-JWT-Router
to append your user onto Flask's global context (or g
). Therefore we have provided a
utility method that returns a headers Dict that you can then use in your test view handler
request. This example is using the Pytest library:
from flask_jwt_router import (
BaseJwtRoutes,
JwtRoutes,
Google,
GoogleTestUtil,
TestRoutingMixin,
)
class TestJwtRoutes(TestRoutingMixin, BaseJwtRoutes):
pass
if not Config.E2E_TEST:
jwt_routes = JwtRoutes()
else:
jwt_routes = TestJwtRoutes()
if not config.E2E_TEST:
jwt_routes.init_app(
app,
google_oauth=oauth_options,
strategies=[Google],
entity_models=[MyModel],
)
else:
jwt_routes.init_app(
app,
google_oauth=oauth_options,
strategies=[GoogleTestUtil],
entity_models=[MyModel],
)
@pytest.fixture()
def client():
# See https://flask.palletsprojects.com/en/1.1.x/testing/ for details
def test_blogs(client):
google = jwt_routes.get_strategy("GoogleTestUtil")
user_headers = google.create_test_headers(email="user@gmail.com")
rv = client.get("/blogs", headers=user_headers)
If you are not running a db in your tests, then you can use the entity
kwarg.
For example:
# user is an instantiated SqlAlchemy object
google = jwt_routes.get_strategy("GoogleTestUtil")
user_headers = google.create_test_headers(email="user@gmail.com", entity=user)
# user_headers: { "X-Auth-Token": "Bearer <GOOGLE_OAUTH2_TEST>" }
If you require more than one request to a Flask view handler in a single unit test, then set the scope kwarg to application. (Default is function). If you are testing different entities within a single unit test method or function then you must pass in your entity. For example:
my_entity = User(email="user@gmail.com") # If you're testing against a real db, make sure this is an entry in the db
google = jwt_routes.get_strategy("GoogleTestUtil")
_ = google.create_test_headers(email="user@gmail.com", scope="application", entity=my_entity)
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.
Please make sure to update tests as appropriate.
Make sure you have Python versions: 3.6
, 3.7
, 3.8
Then run:
tox
To check the docs look good locally you can run:
make html
FAQs
Flask JWT Router is a Python library that adds authorised routes to a Flask app
We found that flask-jwt-router demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.