Here’s the updated README with a focus on the features, including the use of jsonwebtoken under the hood and KID rotation support.
Rust-Based RSA JWT Library
This library offers a high-performance, Rust-based JWT solution with Python bindings via PyO3. Designed for security and speed, it incorporates advanced features like KID rotation, blocking claims, and TTL enforcement.
Features
-
Powered by
jsonwebtoken:- The library leverages the jsonwebtoken crate, a popular and robust JWT library in Rust.
- Provides support for industry-standard algorithms (
RS256,HS256, and more).
-
KID Rotation:
- Supports Key ID (KID) rotation, allowing seamless switching between keys without disrupting existing tokens.
- Keys are managed via
KeyStore, where each key pair can be registered with a uniquekid.
-
Custom Validation Rules:
- Claim Blocking: Reject tokens containing specific blocked values.
- Claim Matching: Ensure claims match predefined expected values.
- TTL Enforcement: Enforce a time-to-live (TTL) for tokens.
-
Exception Handling:
- Provides detailed Python exceptions for better catching.
-
High Performance:
- Faster token generation and validation compared to PyJWT.
Installation
-
Clone the repository:
git clone <repository-url> cd <repository-directory>
-
Install dependencies:
pip install maturin
-
Build and install the Python package:
maturin develop -
Verify installation:
python -c "import key_manager; print('Installed successfully!')"
Quick Start
Example Usage
import time
from datetime import datetime, timedelta, timezone
from key_manager import KeyManager, KeyStore, TokenValidation, BlockedKeyError, MissingMatchClaimError, ExpiredToken
# Load keys
private_key_path = "path/to/private_key.pem"
public_key_path = "path/to/public_key.pem"
# Prepare claims
exp = datetime.now(timezone.utc) + timedelta(hours=1)
claims = {
"sub": "user123",
"custom_claim": "example_value",
"exp": int(exp.timestamp()),
"iat": int(time.time()),
}
# Initialize KeyStore and KeyManager
key_store = KeyStore()
key_store.load_keys("default", private_key_path, public_key_path, "RS256", is_default=True)
key_manager = KeyManager(key_store)
# Generate a token
token = key_manager.generate_token_by_kid("default", claims)
print("Generated Token:", token)
# Validate the token with custom rules
validation = TokenValidation()
validation.claims = {"custom_claim": "example_value"} # Require exact match
validation.block = {"is_admin": ["False"]} # Block if "is_admin" is False
validation.ttl = 60 # Enforce TTL of 60 seconds
try:
decoded = key_manager.verify_token_by_kid(token, "default", validation)
print("Token is valid. Decoded claims:", decoded)
except BlockedKeyError as e:
print("BlockedKeyError:", e)
except MissingMatchClaimError as e:
print("MissingMatchClaimError:", e)
except ExpiredToken as e:
print("ExpiredToken:", e)
except Exception as e:
print("Validation failed:", e)
Key Rotation
Key rotation is seamlessly supported:
- Register multiple keys using
KeyStore.register_keys()orKeyStore.load_keys()methods. - Assign a unique
kidto each key. - Specify the desired
kidduring token generation and validation.
Benchmarking
The provided test script compares the performance of this library against PyJWT.
Run Benchmark
python benchmark.py
Expected Output
Benchmarking PyJWT vs Rust-based RSA JWT
PyJWT:
Generation time: 0.001234 seconds
Validation time: 0.001567 seconds
Rust-based RSA JWT:
Generation time: 0.000789 seconds
Validation time: 0.000923 seconds
Performance Comparison:
Token generation: Rust is 1.56x faster than PyJWT
Token validation: Rust is 1.70x faster than PyJWT
Exception Types
| Exception Name | Description |
|---|---|
BlockedKeyError |
Raised when a token contains blocked claim values. |
MissingMatchClaimError |
Raised when a claim value doesn't match the expected value. |
ExpiredToken |
Raised when the token exceeds the enforced TTL. |
InvalidTokenError |
Raised for general invalid token errors. |
ExpiredSignatureError |
Raised when the token has expired. |
DecodeError |
Raised for decoding errors. |
Testing
Save the provided Python script as benchmark.py and update paths for your key files.
Let me know if further updates are needed!
Metadata
Release files for key-manager 0.1.10
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| key_manager-0.1.10.tar.gz | 33.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| key_manager-0.1.10-cp311-cp311-manylinux_2_28_aarch64.whl | CPython 3.11 | CPython 3.11 | Linux glibc 2.28+ ARM64 | Details |
Total release size: 1.0 MB
Release files / key_manager-0.1.10.tar.gz
| Download URL | key_manager-0.1.10.tar.gz |
|---|---|
| Size | 33.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1bd2b97ee2ba0925887ec6476fe52e35839b9097bc90f0299d9afac75f37c079
|
|
BLAKE2b-256 checksum How to use checksums |
8b7ef84726d307e71e679da132b9351057802401696366b3523e75795378ebf6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
maturin/1.7.8
|
Release files / key_manager-0.1.10-cp311-cp311-manylinux_2_28_aarch64.whl
| Download URL | key_manager-0.1.10-cp311-cp311-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 979.1 kB |
| Tags | CPython 3.11 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
9c2aa9c07c403f27afbb9a696f58d8a0c66e4911ec9f8a9a26379523d6e84165
|
|
BLAKE2b-256 checksum How to use checksums |
8b4316e30a6317076e1e0524a6ac2200000812c79162fd7c9741cf43ac6cf57a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
maturin/1.7.8
|
Security for key-manager 0.1.10
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.