Add comprehensive guide for configuring Microsoft Entra ID as OIDC provider for Apicurio Registry 3.1 #7061
+1,221
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Description
This guide provides detailed instructions for replacing Keycloak with Microsoft Entra ID External Tenants as an identity provider for Apicurio Registry 3.1.0. The document covers critical configuration differences between Entra ID and Keycloak, particularly around JWT token structure and the roles claim.
Key topics covered:
Test Plan
docs/guides/2025/securing-apicurio-registry-with-microsoft-entra-id-external-tenants.md