Feature Overview (aka. Goal Summary)

An elevator pitch (value statement) that describes the Feature in a clear,
concise way.

Now that we have the extension points added to the RBAC backend plugin, We can create an RBAC backend module that will allow us to query information from Keycloak to be loaded into RBAC.

Goals (aka. expected user outcomes)

The observable functionality that the user now has as a result of receiving
this feature. Include the anticipated primary user type/persona and which
existing features, if any, will be expanded.

The user would be able to configure the RBAC backend plugin and RBAC backend module Keycloak to connect to an existing Keycloak instance. From there the module would be able to automatically retrieve role (and possibly permission) information from Keycloak and send it to the RBAC plugin to be added. 

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order
to be considered complete. If the feature spans across releases then good
to have scope for each release with acceptance criteria. Be sure to
include nonfunctional requirements such as security, reliability,
performance, maintainability, scalability, usability, etc.

• RBAC backend module Keycloak
  • Can connect to a Keycloak instance
  • Can retrieve roles from the Keycloak instance
  • Can retrieve permissions from the Keycloak instance
  • Can modify the roles (and possibly permissions) to have them ready for ingestion by RBAC backend plugin
  • Can call extension points from RBAC backend plugin to load information
• Tests
  • E2E
  • Unit tests for the RBAC backend module Keycloak
• Documention
• Demo

Out of Scope (Optional)

High-level list of items that are out of scope.

<your text here>

Customer Considerations (Optional)

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.

<your text here>