Goal:

• RH SSO will enter End of Maintenance Support in June 2025. We need to remove the related procedures from the documentation and ensure docs and test support for Red Hat build of Keycloak setup before that happens.

Acceptance Criteria:

• RHBK setup is documented downstream (it's currently published only upstream in Configuring SSO and 2FA with Quarkus-based Keycloak in Foreman
• RHBK setup is tested
• RHSSO setup is removed from documentation (currently published at https://docs.redhat.com/en/documentation/red_hat_satellite/6.16/html-single/configuring_authentication_for_red_hat_satellite_users/index#configuring-sso-and-2fa-with-keycloak-wildfly-in-project_keycloak-wildfly )

Open questions:

• Q: Should QE make parametrized tests that run against both RHSSO and RHBK, setup differing based on parameter? Or should QE replace RHSSO by RHBK, stopping RHSSO testing?
  A: Yes.
• Q: Should the tests be marked as PIT tests?
  A: Ideally yes, otherwise they won't really run.
• Q: RHBK uses a different URL than RHSSO and keycloak-httpd-client-install couldn't work with that so we have a workaround documented upstream. But keycloak-httpd-client-install has since been updated (see comments in https://github.com/theforeman/foreman-packaging/pull/10720). Should we drop the workaround from docs and if so, then when?
  A: Keep workaround for rhel9.y where y<6, describe new way for 9.6 and later
• Q: Should we bump keycloak-httpd-client-install in our repos for rhel8?
  sort of A: Version in rhel 9.6 will be newer, therefore it will "win" over the package we may or may not currently be shipping. We could force the update everywhere, but then we'd end up with having to maintain it.
• Q: How does RHSSO EOL align with older Satellites' lifecycles? Should we do something about compatibility between older Satellites and RHSSO/RHBK?
  A: AI Adam fill this
• Q: Do we need changes in RHSSO configuration steps?
  A: Yes, we need to change the steps in RHSSO installer for RHEL 9.6 since the default path changed
• Q: 

Summary of the current QA coverage for RHSSO and RHBK:

• Automation runs against RHSSO
• The team has a stable instance of RHBK, QE used it for some manual tests, it basically works
• Automation doesn't run against RHBK
• RHBK is very similar to RHSSO and QE expects tests in automation to be reusable in RHBK
• To run against RHBK, setup fixtures need to be made for RHBK. Then we need to evaluate whether tests pass with only setup change, or changes to tests will be necessary

QE Automation Tracker for https://issues.redhat.com/browse/SAT-29434