Skip to main content

scalio-tenant

Tenant connection shared by the Scalio apps (scalio-docs ADR 0036). The app makes its own certificate; the private key never leaves the instance. The customer's admin runs a setup script that creates the app registration «Scalio Lesen» (read) or «Scalio Schreiben» (write) in their own tenant with only the public certificate, and pastes the printed connection code back into the app.

import scalio_tenant as st

cert = st.new_certificate("Scalio Lesen (rosetta.kunde.ch)")      # store cert_pem, encrypt key_pem
text = st.script(st.read_profile(), cert, "rosetta.kunde.ch")    # show to the admin (Azure Cloud Shell)
conn = st.parse_code(pasted, st.read_profile(), cert)            # tenant, client_id, object_id, key_id
info = st.check(conn["tenant"], conn["client_id"], cert, st.read_profile())  # organization, missing roles
token = st.get_token(conn["tenant"], conn["client_id"], cert)
if cert.due():                                                   # 30 days before expiry
    r = st.renew(conn["tenant"], conn["client_id"], conn["object_id"], conn["key_id"], cert, name)
    # store r["cert"] and r["key_id"] at once
  • permissions.READ_ROLES: the Graph application permissions of «Scalio Lesen». write_profile(roles) takes the roles of the booked modules (the app knows them).
  • read_profile(exchange_teams=True) (0.3.0): also Exchange.ManageAsApp and the Entra role Global Reader, for the Exchange and Teams admin APIs (tokens for st.EXCHANGE and st.TEAMS). check reports what is missing.
  • GDAP (0.3.0): msp_profile(read_profile(...)) makes one multi-tenant registration «Scalio MSP» in the MSP's partner tenant; gdap_customers(partner, client_id, cert) lists the customers with an active GDAP relationship; consent_script(profile, client_id, customer) is run by the MSP's admin once per customer (GDAP roles Application Administrator and Privileged Role Administrator) and grants the permissions there. Tokens for a customer: get_token(customer_tenant, msp_client_id, msp_cert).
  • The app stores the certificate and the encrypted key itself; this package keeps nothing.
  • Renewal uses Graph addKey/removeKey with a proof signed by a key on the registration: no extra permission and no admin.

Tests run offline (pip install -e ".[dev]", pytest, ruff check .); Microsoft is faked with httpx.MockTransport.

Metadata

Release files for scalio-tenant 0.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for scalio-tenant 0.3.0
File Size Uploaded Provenance Actions
scalio_tenant-0.3.0.tar.gz 18.3 kB With provenance Details for scalio_tenant-0.3.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for scalio-tenant 0.3.0
File Interpreter ABI Platform Actions
scalio_tenant-0.3.0-py3-none-any.whl Python 3 none any Details for scalio_tenant-0.3.0-py3-none-any.whl

Total release size: 33.7 kB

Release files / scalio_tenant-0.3.0.tar.gz

Download URL scalio_tenant-0.3.0.tar.gz
Size 18.3 kB
Tags Source
SHA-256 checksum
How to use checksums
f1c43ae1c8c2b631ca1287acefeadcb0c3e1a53ca18122e9e3d53b31dd20dc55
BLAKE2b-256 checksum
How to use checksums
50c70ae365ab22f4f213be8fa084007cfd0b8fa65cdc12dc8bf0d0dcf7a9673d
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 31, 2026.

Transparency log

Release files / scalio_tenant-0.3.0-py3-none-any.whl

Download URL scalio_tenant-0.3.0-py3-none-any.whl
Size 15.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e1cc6230c6f1375c429847d438522e62c78f925d997b08a0d5e15260711f34c9
BLAKE2b-256 checksum
How to use checksums
ee312b36ab221436c8214985e5a7ad556ceb6c158a9616ef6b24ce6657e5b30a
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 31, 2026.

Transparency log

Security for scalio-tenant 0.3.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.

Select from 2 files

Attestation for scalio_tenant-0.3.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 31, 2026.

Transparency log

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page