ssr
Shared-Secret Requests: A simple HTTP authentication library using shared secrets.
Overview
The ssr library exposes a simple set interfaces that facilitate server-server
authentication using a shared secret. This shared secret or secret_key is used
to generate a public key, using a client id and timestamp. The combination of the
client id, timestamp and public key form a signature that a host server can use
to verify the identity of the client server.
Scope
The scope of this project is limited to inter-app authentication e.g. to support RESTful data transfer between micro-services. Logistics around managing secrets is noot included in the scope of this project. For tools to manage secrets you can look into:
Installation
pip install ssr
Usage
SSR Client
TBD
Requests Session
import ssr
session = ssr.Session(
secret_key=os.environ.get('APP_SECRET_KEY')
)
response = session.get(
'https://myblog.com/api/post_reports/',
params={'q': 'auth'}
)
Base Authentication
TBD
Metadata
Release files for ssr 0.1.0
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 | Actions |
|---|---|---|---|---|
| ssr-0.1.0.tar.gz | 9.5 kB | Without provenance | Details for ssr-0.1.0.tar.gz |
Release files / ssr-0.1.0.tar.gz
| Download URL | ssr-0.1.0.tar.gz |
|---|---|
| Size | 9.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0bfc86c52d53cca0152717bed81c3a587959095b4b0fee4cc751b4cc1877b594
|
|
BLAKE2b-256 checksum How to use checksums |
f4f7b1fdbc0999f2695d1258f3924e1a7e2f3bcf4057d88737ebe7b90a57a0a8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for ssr 0.1.0
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.