Apicurio Registry authenticates users and clients with OpenID Connect and supports role-based authorization. These posts show how to connect it to specific identity providers and how the authentication model has evolved.
Securing your API schemas and event definitions is a critical part of managing any Apicurio Registry deployment. Until now, every built-in way to require a username and password depended on infrastructure outside the registry: OpenID Connect (OIDC) needs an identity...
In a previous post, we showed how to connect Apicurio Registry directly to OpenShift’s built-in OAuth server. It worked for API-level authentication and role-based authorization, but three important features were broken: UI login, principal identity (artifact ownership), and owner-based authorization....
If you’re running Apicurio Registry on OpenShift, you might be wondering: can I use OpenShift’s built-in OAuth server for authentication instead of deploying a separate identity provider like Keycloak? The answer is yes — with some caveats. In this post,...
Hey everyone - I wanted to share something we’ve been working on that I think some of you might find interesting. We’ve created a proof of concept showing how to externalize authentication and authorization for Apicurio Registry using a reverse...
Hey everyone, in our previous blog post, we covered the authentication process using Azure Entra ID (formerly Azure AD). In this technical guide, we will provide a step-by-step approach to securing both the Apicurio Registry UI and API. By the...
Hey everyone, in Apicurio Registry 2.0.0. Finally we’ve introduced support for some new security features. In this blog post, I will explain these concepts and show you how to configure them.
Reference documentation: Configuring Apicurio Registry security.
Other topics: Migrating to Apicurio Registry 3.x · AI agents, MCP and LLM artifacts · Apache Kafka, SerDes and Kafka Connect