A powerful, simple, and async security library for Sanic.
Project description
Sanic Security
A powerful, simple, and async security library for Sanic.
Documentation
·
Report Bug
·
Request Feature
Table of Contents
About The Project
Sanic Security is an authentication and authorization library made easy, designed for use with Sanic. This library is intended to be easy, convenient, and contains a variety of features:
- Easy login and registering
- Captcha
- SMS and email verification
- JWT
- Password recovery
- Wildcard permissions
- Role permissions
- Blueprints
- Completely async
This repository has been starred by Sanic's core maintainer:
Getting Started
In order to get started, please install pip.
Prerequisites
- pip
sudo apt-get install python3-pip
Installation
- Install pip packages
pip3 install sanic-security
Usage
Once Sanic Security is configured and good to go, implementing is easy.
Initial Setup
First you have to create a configuration file called security.ini in the project directory. Make sure Python's working directory is the project directory. Below is an example of its contents:
WARNING: You must set a custom secret or you will compromise your encoded sessions.
[SECURITY]
secret=05jF8cSMAdjlXcXeS2ZJUHg7Tbyu
captcha_font=source-sans-pro.light.ttf
[BLUEPRINT]
register_route=api/auth/register
login_route=api/auth/login
verify_route=api/auth/verify
logout_route=api/auth/logout
captcha_request_route=api/capt/request
captcha_img_route=api/capt/img
[TORTOISE]
username=admin
password=8UVbijLUGYfUtItAi
endpoint=example.cweAenuBY6b.us-north-1.rds.amazonaws.com
schema=exampleschema
models=sanic_security.models, example.models
engine=mysql
generate=true
[TWILIO]
from=12058469963
token=1bcioi878ygO8fi766Fb34750e82a5ab
sid=AC6156Jg67OOYe75c26dgtoTICifIe51cbf
[SMTP]
host=smtp.gmail.com
port=465
from=test@gmail.com
username=test@gmail.com
password=wfrfouwiurhwlnj
tls=true
start_tls=false
You may remove each section in the configuration you aren't using. For example, if you're not utilizing Twillio you can
delete the TWILLIO
section.
Once you've configured Sanic Security, you can initialize Sanic with the example below:
initialize_security_orm(app)
if __name__ == "__main__":
app.run(host="0.0.0.0", port=8000, debug=True)
All request bodies must be sent as form-data
. The tables in the below examples represent example request form data.
Authentication
- Registration (With all verification requirements)
Phone can be null or empty.
Key | Value |
---|---|
username | test |
test@test.com | |
phone | 19811354186 |
password | testpass |
captcha | Aj8HgD |
@app.post("api/auth/register")
@requires_captcha()
async def on_register(request, captcha_session):
two_step_session = await register(request)
await two_step_session.text_code() # Text verification code.
await two_step_session.email_code() # Or email verification code.
response = json("Registration successful!", two_step_session.account.json())
two_step_session.encode(response)
return response
- Registration (Without verification requirements)
Phone can be null or empty.
Key | Value |
---|---|
username | test |
test@test.com | |
phone | 19811354186 |
password | testpass |
@app.post("api/auth/register")
async def on_register(request):
account = await register(request, verified=True)
return json("Registration Successful!", account.json())
- Verify Account
Key | Value |
---|---|
code | G8ha9nVae |
@app.post("api/auth/verify")
@requires_two_step_verification(allow_unverified=True)
async def on_verify(request, two_step_session):
await verify_account(two_step_session)
return json("You have verified your account and may login!", two_step_session.json())
- Login
Key | Value |
---|---|
test@test.com | |
password | testpass |
@app.post("api/auth/login")
async def on_login(request):
authentication_session = await login(request)
response = json("Login successful!", authentication_session.account.json())
authentication_session.encode(response)
return response
- Requires Authentication
@app.get("api/auth/authenticate")
@requires_authentication()
async def on_authenticated(request, authentication_session):
return json(f"Hello {authentication_session.account.username}! You are now authenticated.",
authentication_session.account.json())
- Logout
@app.post("api/auth/logout")
@requires_authentication()
async def on_logout(request, authentication_session):
await logout(authentication_session)
response = json("Logout successful!", authentication_session.account.json())
return response
Captcha
You must download a .ttf font for captcha challenges and define the file's path in security.ini.
Captcha challenge example:
- Request Captcha
@app.post("api/captcha/request")
async def on_request_captcha(request):
captcha_session = await request_captcha(request)
response = json("Captcha request successful!", captcha_session.json())
captcha_session.encode(response)
return response
- Captcha Image
@app.get("api/captcha/img")
async def on_captcha_img(request):
captcha_session = await CaptchaSession().decode(request)
return await captcha_session.get_image()
- Requires Captcha
Key | Value |
---|---|
captcha | Aj8HgD |
@app.post("api/captcha/attempt")
@requires_captcha()
async def on_captcha_attempt(request, captcha_session):
return json("Captcha attempt successful!", captcha_session.json())
Two-Step Verification
- Request Two-step Verification (Creates and encodes a two-step session)
Requesting verification should be conditional. For example, an account that is logging in is unverified and requires verification.
For verification requests and endpoints requiring verification, an allow_unverified
(defaulted to false) parameter is available to allow unverified accounts access to the endpoint.
Key | Value |
---|---|
test@test.com | |
captcha | Aj8HgD |
@app.post("api/verification/request")
@requires_captcha()
async def on_request_verification(request, captcha_session):
two_step_session = await request_two_step_verification(request)
await two_step_session.text_code() # Text verification code.
await two_step_session.email_code() # Or email verification code.
response = json("Verification request successful!", two_step_session.json())
two_step_session.encode(response)
return response
- Resend Two-step Verification Code (Does not create new two-step session, only resends existing session code)
@app.post("api/verification/resend")
async def on_resend_verification(request):
two_step_session = await TwoStepSession().decode(request)
await two_step_session.text_code() # Text verification code.
await two_step_session.email_code() # Or email verification code.
return json("Verification code resend successful!", two_step_session.json())
- Requires Two-Step Verification
Key | Value |
---|---|
code | G8ha9nVa |
@app.post("api/verification/attempt")
@requires_two_step_verification()
async def on_verified(request, two_step_session):
response = json("Two-step verification attempt successful!", two_step_session.json())
return response
Authorization
Sanic Security comes with two protocols for authorization: role based and wildcard based permissions.
Role-based access control (RBAC) is a policy-neutral access-control mechanism defined around roles and privileges. The components of RBAC such as role-permissions, user-role and role-role relationships make it simple to perform user assignments.
Wildcard permissions support the concept of multiple levels or parts. For example, you could grant a user the permission
printer:query
. The colon in this example is a special character used to delimit the next part in the permission string. In this example, the first part is the domain that is being operated on (printer), and the second part is the action (query) being performed.
This concept was inspired by Apache Shiro's implementation of wildcard based permissions.
Examples of wildcard permissions are:
admin:add,update,delete
admin:add
admin:*
employee:add,delete
employee:delete
employee:*
- Require Permissions
@app.post("api/auth/perms")
@require_permissions("admin:update", "employee:add")
async def on_require_perms(request, authentication_session):
return text("Account permitted.")
- Require Roles
@app.post("api/auth/roles")
@require_roles("Admin", "Moderator")
async def on_require_roles(request, authentication_session):
return text("Account permitted")
Error Handling
@app.exception(SecurityError)
async def on_error(request, exception):
return exception.response
Middleware
- Cross Site Scripting Protection Middleware
The HTTP X-XSS-Protection response header is a feature that stops pages from loading when they detect reflected cross-site scripting (XSS) attacks.
@app.middleware("response")
async def xxs_middleware(request, response):
xss_prevention_middleware(request, response)
- Https Redirection Middleware
Redirects all http requests to https.
@app.middleware("request")
async def https_middleware(request):
return https_redirect_middleware(request)
Blueprints
Sanic Security blueprints contain endpoints that allow you to employ fundamental authentication and verification into your application with a single line of code.
- Implementation
Blueprint containing all security endpoints.
app.blueprint(security)
- Endpoints
Method | Endpoint | Info |
---|---|---|
POST | api/auth/register | A captcha is required. Register an account with an email, username, and password. Once the account is created successfully, a two-step session is requested and the code is emailed. |
POST | api/auth/login | Login with an email and password. A two-step session is requested when the account is not verified and the code is emailed |
POST | api/auth/verify | Verify account with a two-step session code found in email. |
POST | api/auth/logout | Logout of logged in account. |
POST | api/capt/request | Requests new captcha session. |
GET | api/capt/img | Retrieves captcha image from existing captcha session. |
Testing
You may test Sanic Security manually with postman or run automated unit tests.
Make sure the test Sanic instance (test/server.py
) is running on your machine as both postman, and the unit tests operate as a test client.
Then run the unit tests (test/tests.py
) or test with postman via clicking the button below.
Roadmap
Keep up with Sanic Security's Trello board for a list of proposed features, known issues, and in progress development.
Contributing
Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are greatly appreciated.
- Fork the Project
- Create your Feature Branch (
git checkout -b feature/AmazingFeature
) - Commit your Changes (
git commit -m 'Add some AmazingFeature'
) - Push to the Branch (
git push origin feature/AmazingFeature
) - Open a Pull Request
License
Distributed under the GNU General Public License v3.0. See LICENSE
for more information.
Versioning
0.0.0.0
Major.Minor.Revision.Patch
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
File details
Details for the file sanic-security-0.10.4.0.tar.gz
.
File metadata
- Download URL: sanic-security-0.10.4.0.tar.gz
- Upload date:
- Size: 35.2 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/3.4.2 importlib_metadata/4.6.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.61.2 CPython/3.8.10
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | 6909b63f74c1fdfbb6a95d68699077fc545df23d9c55ac6f280b69cda05eb6eb |
|
MD5 | 5badfdb56a9cc72dfcc2f42c946128d9 |
|
BLAKE2b-256 | c0822f182671d9b1ac3cc49b33e5c56e3fee3dd1b326f0d71148049b18fa12e8 |