How enablebanking/open_banking_eidas_broker works
Project type and purpose
• This is a containerized, full-stack API microservice (“Open Banking eIDAS broker”) implemented in Python 3.11 using FastAPI.
• It exposes three REST endpoints (/sign, /makeRequest, /health) over mTLS, offloading signature generation and mutually authenticated HTTP calls to downstream ASPSP (Account Servicing Payment Service Provider) APIs.
File structure
• Top level:
• Dockerfile, run.sh, run.py, nginx.conf → container build & runtime
• openapi.json → API contract
• requirements.txt → Python deps
• trusted_aspsps_certs/ → built-in ASPSP CA certs
• app/ → service code & tests
• examples/ → usage examples
• .github/workflows/ → CI (test, image-scan)
• app/ contains:
• main.py (FastAPI app & routing)
• server_platform.py (ServicePlatform: sign_with_key, make_request)
• key_loader.py (abstraction for loading certs & keys from FS or ENV)
• models.py (Pydantic request/response schemas)
• tests/ → unit & integration tests
• Deployment config: nginx.conf for mTLS frontend, Gunicorn/Uvicorn worker, Docker build binds volumes for broker TLS and open banking certs.
README for additional insights
• Describes end-to-end flows:
a. Client calls POST /sign → broker signs data with a QSealC cert
b. Client calls POST /makeRequest → broker opens mTLS connection to ASPSP using QWAC cert
c. Certificates & keys are never shipped to the client; loaded server-side
• Outlines certificate generation & mounting strategy, environment variables for encrypted keys, custom trust store overrides.
• CI pipelines enforce tests and image scanning.