How keycloak/keycloak-client works
Main Components
• Client Libraries:
• admin-client: Provides functionality for invoking the Keycloak Admin REST API.
• authz-client: Provides functionality for invoking the Keycloak Authorization API.
• policy-enforcer: Implements the access decision enforcement logic and consumes the authorization-client.
• client-common-synced: Contains shared classes, utilities, and JSON mappings that are used by all client modules.
• Supporting Modules:
• docs: Contains guides and documentation for how the libraries are used.
• CI/CD and Build Infrastructure:
• .github directories (workflows, actions, and scripts) for automated builds, tests, sync operations, and release processes.
• Maven build configuration files (pom.xml in several modules, build scripts, etc.).
Establish Relationships & Data Flows
• Internal Library Dependencies:
• External Dependencies:
Architectural Patterns & Design Principles
• Modularization: The project is clearly divided into modules to separate concerns (API invocation, enforcement, utilities, tests, documentation).
• CI/CD Integration: Although not part of the business logic, the GitHub workflows and actions form an external pipeline that triggers builds, tests, and synchronization scripts.