redb.Identity Adds gRPC Transport for OpenID Server Alongside Existing HTTP Facade
redb.Identity has added a gRPC facade to its OpenID server, placing it alongside the existing HTTP transport on the same core routes. The server remains transport-agnostic: all authorization logic resides behind direct-vm://identity-* addresses, and both HTTP and gRPC now act as interchangeable facades over this kernel.
The new surface implements the protocol operations required by relying parties: Token at /identity.v1.Identity/Token (RFC 6749 §3.2), Introspect (RFC 7662), Revoke (RFC 7009), UserInfo (OIDC Core §5.3), Discovery, and Jwks (RFC 7517). A gRPC health check is also exposed via grpc.health.v1.Health/Check. Forty administrative operations across five services (Users, Applications, Groups, Scopes, Tokens) are available on a dedicated management port.
Requests accept the same key-value pairs defined by the RFCs plus a map<string, string> for extensions. Responses type the fields fixed by the specifications and place open sets such as claims into google.protobuf.Struct. OAuth errors are returned as gRPC status codes (UNAUTHENTICATED, PERMISSION_DENIED, RESOURCE_EXHAUSTED, INVALID_ARGUMENT) with the original error code and correlation identifier carried in trailers.
The same token issued through dynamic client registration over HTTP is accepted by the gRPC endpoint and yields identical authorization decisions. Scope evaluation occurs once inside the kernel at direct-vm://identity-authz-check, eliminating the risk of divergent policy between transports.
Browser flows (authorize, login, consent, MFA), DPoP proofs (RFC 9449), and user self-service remain exclusively on HTTP. The gRPC listener uses its own port because it requires HTTP/2 while the HTTP facade supports both HTTP/1.1 and HTTP/2.
Configuration is placed in the shared context.json under the identity.grpc section, allowing independent host, port, TLS, and compression settings. The EmitHttpCompatHeaders flag is enabled by default to preserve IP-based rate limiting and device metadata collection.
Related articles
TLS Fingerprinting Explained: From Handshakes in TLS 1.2/1.3 to JA3, JA4, HTTP/2 Analysis and uTLS Evasion
The article provides an in-depth examination of how TLS handshakes reveal client identity even before any HTTP data is sent. It traces the evolution from early SSL versions developed by Netscape to modern TLS 1.3, highlighting how elliptic curve cryptography and AEAD ciphers reduced latency while increasing observability challenges for defenders. Detailed breakdowns show why JA3 hashes became unreliable due to GREASE randomization and extension ordering changes, prompting the shift to the more robust JA4+ family that uses sorted, GREASE-resistant blocks for stable fingerprints. The piece also covers HTTP/2 fingerprinting signals and practical tools such as uTLS in Go for mimicking browser TLS stacks and Finch for traffic analysis. Real Wireshark captures of Client Hello packets to GitHub illustrate how Cloudflare and WAF systems detect scripted clients despite matching User-Agent headers. Overall, the content serves as both a historical overview and a hands-on guide for security engineers working on bot mitigation and traffic obfuscation.
Centralized Secret Management: Comparing Eight Tools for DevOps and Spring Boot Applications
The article examines the challenges of managing secrets such as passwords, API tokens, and SSH keys across development, CI/CD pipelines, and production environments. It explains how centralized secret registries solve issues like scattered .env files, outdated credentials, and lack of audit trails while emphasizing that delivery mechanisms to applications must be chosen separately. Key concepts including static versus dynamic credentials, leases, rotation, and machine identities are defined to help teams implement least-privilege access. The review compares Infisical, HashiCorp Vault, OpenBao, Doppler, 1Password CLI, Bitwarden Secrets Manager, Passbolt, and Yandex Lockbox across deployment models, offline support, and integration options. Special attention is given to CLI run commands that avoid plaintext files, Spring Cloud Vault integration, and the trade-offs between SaaS convenience and self-hosted control. Practical recommendations focus on separating developer and machine access as well as development and production environments.
Opera Rolls Out Local AI Processing via WebAI Standard in Opera One Browser
Opera has introduced an early implementation of WebAI, a proposed web standard that enables websites and extensions to run AI models directly on the user's device instead of relying on remote servers. The feature debuts in Opera One and will later expand to Opera GX and Neon. Supported models include Google's Gemma as well as Apple's local foundational model on compatible Mac hardware, with no vendor lock-in. Key capabilities cover text generation, content classification, and analysis of relationships between information fragments. Developers gain the ability to add AI features without building server infrastructure or incurring per-query cloud costs, while users avoid subscriptions to external AI services. All processing occurs locally on an opt-in basis, keeping data off cloud providers, although performance depends on the device's hardware capabilities.
Russian Prosecutor's Office Withdraws Lawsuit Against Timur Turlov and Freedom Holding Corp.
The Tverskoy District Court in Moscow terminated proceedings after the Russian Prosecutor General's Office withdrew its administrative claim against Timur Turlov and several related entities. The court accepted the refusal on October 15, 2026, lifted all previously imposed asset restrictions, and ended the case without examining the merits. The original claim sought to seize hundreds of millions of dollars in assets, declare the defendants an extremist organization, and ban their activities in Russia. No reasons for the sudden withdrawal were provided during the preliminary hearing. The decision prevents the Prosecutor General's Office from refiling the same claim against the same parties on identical grounds under Russian administrative procedure rules. Freedom Holding Corp. stated it has no operations or assets in Russia and expressed surprise at the original filing. Timur Turlov, who holds Kazakh citizenship and serves as FIDE president, was listed among the defendants alongside Freedom Holding Corp., Freedom Finance Europe Ltd., and W-Empirical Holding Corp.