Redb.Identity Expands Transport Options with gRPC Integration
The prominent OpenID server, redb.Identity, has significantly enhanced its capabilities by introducing a second transport: gRPC. Previously, the system was described as transport-agnostic, with its core logic residing at direct-vm://identity-* addresses and HTTP serving as the sole facade. This architectural promise has now been substantiated with the practical integration of gRPC.
Unified Operations Across Two Transports
The implementation of gRPC in redb.Identity means that both HTTP and gRPC now utilize the identical core routes, the same issuer, client registry, and token storage. This ensures complete unification: a single token will be accepted and processed identically by both transports, yielding the same verdict. This development is particularly relevant for environments where gRPC has already become a standard for inter-service communication.
Redb Ecosystem Updates and Version 3.7.0 Recall
The redb ecosystem has undergone a series of rapid updates, with three versions released in quick succession: 3.7.0, 3.7.1, and 3.7.2. Version 3.7.0 was subsequently recalled, making 3.7.2 the current stable release. These updates brought substantial changes across key products:
- redb.Route: Introduced its own gRPC-wire protocol.
- redb.Core: Implemented truncation of properties (props) down to the aggregate.
- redb.Tsak: Now closed by default.
- redb.Identity: Gained a second facade with gRPC, marking a pivotal new feature.
All four products within the redb ecosystem are now released under a unified version number, encompassing 66 packages. This update underscores the developers’ commitment to modularity and flexibility, offering users greater choice in communication architecture.
The integration of gRPC into redb.Identity, particularly with unified core routes and token handling across both HTTP and gRPC, represents a significant architectural maturation. This move directly addresses enterprise requirements for low-latency, high-throughput inter-service communication in microservices environments, enhancing its appeal in cloud-native deployments. The consistent issuer and client registry across transports is critical for maintaining security posture and operational simplicity, particularly for OAuth 2.0 and OpenID Connect flows. This positions redb.Identity strongly against other identity providers that may lack this native gRPC fluency.