A small capability-token experiment proving allowed-path reads, refresh, and denial of every unapproved path.
Can a workload use short-lived path-scoped credentials without falling back to ambient credentials?
- short-lived credentials bound to one path prefix
- positive and negative object-access checks
- explicit expiry and refresh behavior
- no environment, metadata, or shared-profile fallback
Requires Python 3.10+.
python -m unittest discover -s tests -v
PYTHONPATH=src python -m credential_isolationThe demo prints deterministic JSON that can be inspected or used as a CI artifact.
- the object store and broker are in-memory test doubles
- real workload identity exchanges belong in provider-specific adapters
A tested GitHub Actions definition is included at ci/github-actions.yml.
Move it to .github/workflows/ci.yml to activate hosted CI. It is kept as a
template because the current GitHub CLI credential cannot modify workflow
files without an additional account authorization.
This is newly written open-source code using synthetic inputs and generic identifiers. It contains no employer source, private data, production configuration, credentials, internal resource identifiers, or private benchmark results.
MIT