scalio-connect
Signed calls between the Scalio apps and Compass. One format ("v2", header Scalio-Signature) for every
direction:
- Compass -> app: control key K3 on
/api/provision/*(replaces the oldX-Provision-Control-Signature) - app -> Compass: instance key on the support intake
/api/support/v1/*(planned)
Contract: scalio-docs interfaces/signed-request-v2.md. Decision: scalio-docs ADR 0020.
What is signed
Scalio-Signature: v=2,kid=k3,ts=1793131200,nonce=vector-nonce-0000000001,sig=<base64 Ed25519>
scalio-sig-v2
<kid>
<METHOD>
<audience = receiver origin, e.g. https://acme.eu.scalionexus.com>
<path and query as sent, e.g. /api/provision/admin>
<ts>
<nonce>
<sha256 of the raw body, hex>
Lines joined by \n, no line break at the end. Time window +-300 s, each (kid, nonce) once.
Because receiver and path are signed, a captured request does not work on another instance or another
endpoint (security review H9).
Usage
from scalio_connect import sign, verify, SignatureError
from scalio_connect.nonces import use_nonce
# sender
headers = sign(private_key, "k3", "POST", "https://acme.eu.scalionexus.com/api/provision/admin", body)
# receiver (raw body bytes, path with query as received)
try:
v = verify(request.headers["Scalio-Signature"], request.method, path_with_query, body,
audiences=["https://acme.eu.scalionexus.com"], keys_for=lambda kid: k3_keys if kid == "k3" else [])
except SignatureError:
raise HTTPException(401)
if not await use_nonce(db, v.kid, v.nonce):
raise HTTPException(401)
audiences are the receiver's own public origins from its configuration. Do not take them from the
Host header.
Development
pip install -e ".[dev]"
ruff check . && pytest -q
tests/vector.json is the shared test vector (throwaway seed). Compass and every app test against the same file.
Release: bump pyproject.toml, CHANGELOG line, merge, then "Publish" (cockpit or Actions) with the version, no v.
Metadata
Release files for scalio-connect 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 |
|---|---|---|---|---|
| scalio_connect-0.1.0.tar.gz | 7.2 kB | With provenance | Details for scalio_connect-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| scalio_connect-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for scalio_connect-0.1.0-py3-none-any.whl |
Total release size: 13.3 kB
Release files / scalio_connect-0.1.0.tar.gz
| Download URL | scalio_connect-0.1.0.tar.gz |
|---|---|
| Size | 7.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e17ab5f061f883529db2828990dfa8ec2710beee2bfb896f25484aefe04caa7d
|
|
BLAKE2b-256 checksum How to use checksums |
06aa8840df4e8d9152f0baf0bbfb973763b9fdc563c2cebb54aa2a9a57ae35d3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / scalio_connect-0.1.0-py3-none-any.whl
| Download URL | scalio_connect-0.1.0-py3-none-any.whl |
|---|---|
| Size | 6.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d26fa2a60e6f366c5333e64bb7f1f259d78bf4d480bfdc83696f44aa578fdeb5
|
|
BLAKE2b-256 checksum How to use checksums |
d56b5842e894d31644163c29c5ba5a2e874f1b233dea553c13906500ed86001a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logSecurity for scalio-connect 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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for scalio_connect-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logA 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.