Feature Overview (aka. Goal Summary)  

Workload identity is a key part of the zero-trust model. The SPIRE project aims to simplify the management and distribution of workload identities in the form of cryptographically verifiable identity documents. There is an increasing interest and uptake in this space within the Cloud native ecosystem.  The goal is to give customers a practical and scalable way to establish trust in a multi-cloud, multi-platform environment. It will strengthen OpenShift’s security capabilities and value-add as organizations harden their security policies. 

Provide SPIRE federation with Keycloak for seamless authentication with sevices outside the cluster using Keycloak as their OIDC IDP for machine<>machine workflows

Goals (aka. expected user outcomes)

 ** 

Provide SPIRE federation with Keycloak for seamless authentication with sevices outside the cluster using Keycloak as their OIDC IDP for machine<>machine workflows

Requirements (aka. Acceptance Criteria):

Activity	Dependency	Contacts
Add OIDC Federation support with Keycloak	Support from Keycloak team for OIDC Federation.	Stian Thorgersen Pedro Zapata Fernandez Issa Gueye

 __ 

Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

<To be added> 

Questions to Answer (Optional):

 Keycloak team has identified capabilities it will need to add for seamless integration with SPIRE in a multi-cluster setting. Details here.

Out of Scope

High-level list of items that are out of scope.  Initial completion during Refinement status.

<your text here>

Background

Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

<your text here>

Customer Considerations

Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

<your text here>

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

<your text here>

Interoperability Considerations

Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

<your text here>