On this page
SBB Keycloak
Service Information
Keycloak is a candidate solution building block for the translated DC 3.0 ABB model. It remains candidate until the responsible architects confirm service ownership, support model, and acceptance criteria.
| Item | Information |
|---|---|
| Solution architect | To be assigned during SBB review. |
| CMDB number | Not assigned yet. |
| Service Level Agreement | To be defined during service onboarding. |
| 1st and 2nd line support group | To be defined during service onboarding. |
| 3rd line support group | To be defined during service onboarding. |
| Support response times | To be defined during service onboarding. |
| Managing party | Identity and access management. |
| Contact person | John de Boer. |
Cost and Responsibilities
Cost and responsibility allocation must be confirmed by the managing organizational domain before this SBB is promoted from candidate to selected.
Cost
| Description | Unit | Price |
|---|---|---|
| Platform or service capacity | Consumption metric to be defined | Pricing model to be defined during service design |
Additional Specifications
Cost attribution should support service, tenant, environment, and lifecycle reporting where the ABB exposes self-service consumption.
Responsibilities
Managing Party
The managing party operates the SBB baseline, lifecycle, access model, and integration contracts for the implemented ABBs.
Consuming Party
The consuming party owns workload intent, correct use of the exposed interfaces, data classification, and application-level configuration.
Roadmap and Lifecycle
Lifecycle
| Version | Delivery start date | Delivery end date | Extended support candidate |
|---|---|---|---|
| DC 3.0 candidate baseline | 2026-05-30 | To be defined during review | To be assessed during service review |
Roadmap
| Development status | Plan | Functionality |
|---|---|---|
| Candidate | Confirm architecture owner and service scope | ABB implementation mapping |
| Candidate | Add operational constraints and support model | Production readiness evidence |
Architecture
Application functions:
| ABB | Functionality |
|---|---|
| smart-access | Implements the Smart Access ABB in the DC 3.0 target model. |
| federated-authentication | Implements the Federated Authentication ABB in the DC 3.0 target model. |
Dependencies:
| SBB | Dependency description |
|---|---|
| No direct SBB dependency is recorded yet. | Dependency analysis remains part of SBB review. |
Technical Architecture
Keycloak realizes one or more DC 3.0 ABBs through a concrete product or managed-service pattern. The technical architecture must be expanded by the solution architect before selection.
Technical Documentation
Technical documentation is not attached in this migration pass. It should be linked when the SBB is promoted to selected.