Swarmauri Cert Cfssl
CFSSL-backed certificate service for Swarmauri.
Features
CfsslCertServiceadapter that wraps the CFSSL REST API for signing, parsing, and verifying certificates.- Supports RSA, ECDSA (P-256/P-384), and Ed25519 key material with profile/label routing.
- Optional certificate bundling during verification to ensure complete chains before deployment.
- Detailed parsing utilities that expose SANs, key usage, EKU, Subject/Authority Key Identifiers, and more.
Prerequisites
- Python 3.10 or newer.
- A reachable CFSSL instance (standalone binary, Kubernetes deployment, or the Cloudflare Docker image).
- Valid CFSSL signing profile(s) configured for your use case (e.g.,
www,client,code_signing). - If your CFSSL endpoint is protected, API credentials or access tokens for the headers you plan to use.
Installation
# pip
pip install swarmauri_certs_cfssl
# poetry
poetry add swarmauri_certs_cfssl
# uv (pyproject-based projects)
uv add swarmauri_certs_cfssl
Quickstart: Issue a Certificate
CfsslCertService consumes CSRs generated by other Swarmauri certificate services (for example, the Azure or ACME packages). The example below submits a CSR to CFSSL and saves the issued certificate:
import asyncio
from datetime import datetime, timedelta, timezone
from pathlib import Path
from swarmauri_certs_cfssl import CfsslCertService
from swarmauri_core.crypto.types import KeyRef
async def main() -> None:
service = CfsslCertService(
base_url="https://cfssl.internal",
default_profile="www",
timeout_s=15.0,
auth_header=("X-Auth-Key", "super-secret-token"),
)
csr_bytes = Path("site.csr").read_bytes()
# KeyRef tags allow you to override CFSSL profile/label per request
ca_key = KeyRef(material=b"", tags={"profile": "www", "label": "primary"})
certificate_pem = await service.sign_cert(
csr=csr_bytes,
ca_key=ca_key,
extensions={
"subject_alt_name": {"dns": ["site.example.com", "www.site.example.com"]}
},
not_after=int((datetime.now(timezone.utc) + timedelta(days=90)).timestamp()),
)
Path("site.pem").write_bytes(certificate_pem)
await service.aclose()
if __name__ == "__main__":
asyncio.run(main())
Verify and Parse Certificates
Leverage CFSSL's bundling API to confirm a certificate's trust chain, then inspect the returned metadata:
import asyncio
from pathlib import Path
from swarmauri_certs_cfssl import CfsslCertService
async def verify_and_parse() -> None:
service = CfsslCertService(
base_url="https://cfssl.internal",
use_bundle_for_verify=True,
)
cert_bytes = Path("site.pem").read_bytes()
verification = await service.verify_cert(
cert=cert_bytes,
trust_roots=[Path("root.pem").read_bytes()],
)
print("Valid:", verification["valid"], "Chain length:", verification["chain_len"])
parsed = await service.parse_cert(cert_bytes)
print("Subject CN:", parsed["subject"].get("CN"))
print("SAN entries:", parsed.get("san", {}))
await service.aclose()
if __name__ == "__main__":
asyncio.run(verify_and_parse())
Notes
CfsslCertServicefocuses on signing and validation. Generate CSRs with other Swarmauri services (e.g.,swarmauri_certs_acme,swarmauri_certs_azure) or your existing PKI tooling.- The client uses
httpx.AsyncClient; reuse a service instance for multiple operations and callaclose()when finished to release connections. - Profile and label defaults can be set globally in the constructor or dynamically by attaching tags to the
KeyRefpassed intosign_cert.
Best Practices
- Store CFSSL credentials outside source control (environment variables, secret stores, or Swarmauri state providers).
- Enable TLS on the CFSSL API and pin the certificate when connecting over untrusted networks.
- Use dedicated CFSSL profiles for each application tier and rotate them regularly.
- Capture verification results (e.g., bundle size, expiry) in metrics to stay ahead of certificate renewals.
Metadata
Release files for swarmauri_certs_cfssl 0.2.3
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 |
|---|---|---|---|---|
| swarmauri_certs_cfssl-0.2.3.tar.gz | 11.6 kB | Without provenance | Details for swarmauri_certs_cfssl-0.2.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| swarmauri_certs_cfssl-0.2.3-py3-none-any.whl | Python 3 | none | any | Details for swarmauri_certs_cfssl-0.2.3-py3-none-any.whl |
Total release size: 24.2 kB
Release files / swarmauri_certs_cfssl-0.2.3.tar.gz
| Download URL | swarmauri_certs_cfssl-0.2.3.tar.gz |
|---|---|
| Size | 11.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
20e090612bc84f515c61609122c674a488b129cc08455afbef2ac374d8bcfdb2
|
|
BLAKE2b-256 checksum How to use checksums |
25ae88e73e6857b0c0bd9f53a46d7bb73f408d82278cfc1d21dcf927c7ca54d1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.0 {"installer":{"name":"uv","version":"0.11.0","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / swarmauri_certs_cfssl-0.2.3-py3-none-any.whl
| Download URL | swarmauri_certs_cfssl-0.2.3-py3-none-any.whl |
|---|---|
| Size | 12.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
21338f8a5d4c1b3861ca6c71587d58b2b641f4bae93801b3a88c1462c269edc6
|
|
BLAKE2b-256 checksum How to use checksums |
6af4c1950a32f85efda29dedf67dbca7ae9d187e6f96bca0307b7e639a636a29
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.0 {"installer":{"name":"uv","version":"0.11.0","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for swarmauri_certs_cfssl 0.2.3
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.