TideCloak: Keycloak authority replaced with decentralized Fabric
Original title: TideCloak | Tide Whitepaper Series
TideCloak delivers OIDC-compatible IAM with zero-knowledge auth and E2EE via threshold cryptography on the Tide Fabric.
TideCloak is an IIAM server based on Red Hat Keycloak that removes cryptographic authority from the instance. Signing keys, password hashes and admin overrides are replaced by calls to the decentralized Tide Cybersecurity Fabric. Developers integrate via standard OIDC endpoints and a provided SDK. Compromise of a TideCloak instance requires subverting 14 independent Fabric nodes to forge tokens.
- TideCloak provides identical OIDC/OAuth 2.0 endpoints to Keycloak
- Password verification uses zero-knowledge protocol with no hashes stored
- Root server access reveals no key material
- SDK offers React hooks, middleware and server-side verification
- End-to-end encryption uses tag-based permissions gated by roles
From the original article
7 min read at tide.org
Despite the deep cryptographic complexity required to decentralize trust, enterprise adoption depends entirely on providing a seamless, standard integration path for developers. For a developer evaluating this architecture, one question matters: The answer is an architectural inversion: the more sophisticated the underlying cryptography, the simpler the developer experience can be.
By tide.org via vladislavp · tide.org
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.