DOCSEARCHbyAlgolia
Submit Docs

STOA Platform Documentation

website·Indexed 31 days ago

https://docs.gostoa.dev

Comprehensive directory of STOA Platform documentation, including Getting Started guides, architectural concepts, deployment, API and configuration references, Kubernetes CRDs, and enterprise-specific information. Covers licensing philosophy, security coverage for OWASP API risks, and migration paths.

Tokens
1.7K
Snippets
0
Records
27
Agent score
61%

What's inside STOA

  1. STOA Security Architecture and Defense-in-Depth

    STOA employs a five-layer defense model to secure APIs:

    1. mTLS certificate binding (RFC 8705)
    2. OAuth 2.1 + PKCE
    3. OPA (Open Policy Agent) policy engine
    4. AI guardrails (PII detection, prompt injection prevention)
    5. Immutable audit logging

  2. Migrate from Software AG webMethods to STOA

    Migration from webMethods requires translating IS (Integration Server) Flow language, converting proprietary mediation patterns, and consolidating the service registry.

  3. Deploy an MCP Gateway using Docker Compose

    A quickstart method to get a production-ready MCP gateway running in under 10 minutes. The process includes cloning the repository, configuring the environment, starting the services via Docker Compose, registering an API, and performing first-call verification with health checks.

  4. Harden API Gateway security for production

    Follow this 10-step checklist to secure a production API gateway:

    1. Enforce TLS 1.3 only
    2. Enable HSTS
    3. Implement CORS allowlists
    4. Apply rate limiting to all endpoints
    5. Use URL blocklists for SSRF protection
    6. Set security headers (CSP, X-Frame-Options)
    7. Enforce request size limits
    8. Ensure audit log integrity

  5. Implement Multi-Tenant API Isolation in STOA

    STOA supports several tenant isolation models including namespace-level, row-level, and shard-based isolation. Configuration involves setting up Universal API Contracts (UAC) per tenant and choosing between Keycloak realm-per-tenant or shared-realm patterns for authentication.

  8. Migrate from Broadcom Layer7 API Gateway to STOA

    Migrating from Broadcom Layer7 involves translating 500+ assertion types to OPA/Rego policies, handling WS-Security workloads, using a Keycloak SAML bridge for CA SiteMinder federation, and migrating Kerberos/NTLM authentication.

  9. Execute a zero-downtime API Gateway migration

    Follow this 15-step framework for zero-downtime migration: 1. API inventory and dependency mapping, 2. Shadow mode deployment, 3. OAuth/OIDC identity federation, 4. Policy translation (rate limits, CORS, auth), 5. Canary traffic shifting (1% → 10% → 50% → 100%), 6. Rollback triggers, and 7. Post-migration validation gates.

  10. Scale Multi-Tenant APIs on Kubernetes

    Scaling strategies for STOA include configuring Horizontal Pod Autoscalers (HPA) for tenant traffic spikes, using PgBouncer for connection pooling, implementing per-tenant caching, and defining Kubernetes resource quotas per namespace.

  12. Quick start: Publish your first API with STOA

    Deploy STOA using Docker Compose to create a tenant, register an API, expose it through the MCP Gateway, and perform an authenticated call. This end-to-end process is designed to be completed in approximately 5 minutes.