Eureka
Developer Technologies · Internal · v1.0
Eureka is the capability-token authorization wire protocol for the suite. Ed25519-signed tokens are purpose-bound (e.g. nda:visit:<id>, invoice:<id>), expiring and audience-scoped; verification happens at the edge with no central permission lookup to breach. Every suite service is Eureka-enabled by default.
Business problem
Centralised permission lookups are latency and breach surface; purpose must be cryptographically bound to the token.
Core capabilities
- ▸Ed25519 capability tokens
- ▸Purpose-bound (issuer, audience, purpose)
- ▸Expiring + replay-resistant
- ▸Edge verification — no central lookup
Architecture
Library + sidecar verifier; issuers sign with private key, verifiers check with public set. Purpose string is the authorization scope.
Deployment: Library embedded in each API; verifier at edge.
Licensing: Internal fabric — included with suite.
Evidence & confidence
Confidence: high
- MOBISEC-Portfolio-Executive-Summary.md §8 (Production-ready, unifying thesis)
- D:\MobiseCloud\Projects\Eureka
At a glance
- Platforms
- .NET · API
- Stack
- .NET · Ed25519 · Docker
- Integrations
- OmniTrust Identity · OmniVisit · OmniQuip · OmniParse · OmniSign
- Maturity
- Production (high confidence)
Target customers
- · All MobiSec suite services (internal fabric)
- · Integrators needing capability-delegated auth
Roadmap
Key rotation automation; purpose registry documentation.