curious what people think of decentralised IAM built around Keycloak compatibility
crossposting this from another sub, not trying to spam duplicate threads, just trying to get more feedback from people who know IAM better than me.
ive been following Tide Foundation and their TideCloak project. from what i understand, its a Keycloak-compatible IAM layer built on top of a decentralised security fabric.
the part i find interesting is that it seems to change what the app has to store in the first place.
instead of the usual model where identity data, secrets, or key material ends up depending on one central system, Tide splits trust across the network. so the idea is there isnt one central pile of sensitive stuff sitting there to steal.
from what i understand, devs dont need to store user passwords the normal way or manage one central private key. key material is fragmented across the network, and the password flow uses crypto where the browser aggregates and validates partial results.
the Keycloak-compatible part seems important because most devs probably wont touch decentralised security if the dx is painful or requires relearning the whole auth stack.
curious what people here think of this approach.
does decentralised IAM/security fabric make sense in practice, or does it add too much complexity compared to existing IAM patterns?