This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2062365 - khci won't work with Quarkus-based Keycloak due to missing /auth path
Summary: khci won't work with Quarkus-based Keycloak due to missing /auth path
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: keycloak-httpd-client-install
Version: 8.6
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Tomas Halman
QA Contact: Scott Poore
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-09 16:16 UTC by Jakub Hrozek
Modified: 2023-09-12 13:10 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-12 13:10:58 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-3336 0 None Migrated None 2023-09-12 13:07:19 UTC
Red Hat Issue Tracker RHELPLAN-115050 0 None None None 2022-03-09 16:21:56 UTC
Red Hat Issue Tracker SSSD-4676 0 None None None 2022-05-17 14:38:36 UTC
Red Hat Issue Tracker SSSD-6404 0 None None None 2023-09-09 07:30:25 UTC

Description Jakub Hrozek 2022-03-09 16:16:05 UTC 
Description of problem:
Since Keycloak switched to Quarkus, they also deprecated the /auth endpoint, used by khci. See more at: 
https://www.keycloak.org/migration/migrating-to-quarkus

Version-Release number of selected component (if applicable):
the latest we have in RHEL-8

How reproducible:
not sure yet

Steps to Reproduce:
1. enroll a httpd server with mod_auth_openidc (git grep shows that the /auth endpoint is only used for OIDC)
2.
3.

Actual results:
probably doesn't work

Expected results:
should work

Additional info:
Comment 1 Scott Poore 2022-03-14 22:46:00 UTC 
I think we should use --http-relative-path to match the new option in Keycloak.  In Keycloak this option allows you to add /auth back to the path to help with Migrating from older versions of keycloak that needed it.

I opened a ticket with Keycloak asking how to use that option in production mode.  I was informed that you either have to use it with build stage first or add the --auto-build option to the start stage.  This also applies with starting the Keycloak container in production mode.  The solution I took with my tests was to just add --auto-build and --http-relative-path to the contain run start command like this:

podman run --name keycloak -d \
    -p 8080:8080 \
    -p 8443:8443 \
    -e KEYCLOAK_ADMIN=admin \
    -e KEYCLOAK_ADMIN_PASSWORD=MyPassword123 \
    -e KC_LOG_LEVEL=debug \
    -e KC_HOSTNAME=$(hostname):8443 \
    -e KC_HTTPS_CERTIFICATE_FILE=/etc/x509/https/tls.crt \
    -e KC_HTTPS_CERTIFICATE_KEY_FILE=/etc/x509/https/tls.key \
    -e KC_HTTPS_TRUST_STORE_FILE=/etc/x509/https/truststore.keystore \
    -e KC_HTTPS_TRUST_STORE_PASSWORD=MyPassword123 \
    -e KC_HTTP_RELATIVE_PATH=/auth \
    -v /tmp/https:/etc/x509/https:Z \
    quay.io/keycloak/keycloak:latest start --auto-build

You'll note I used the KC_HTTP_RELATIVE_PATH environmental variable instead of the cli arg.

For reference, this is the ticket I opened upstream asking about using that option in production mode:

https://github.com/keycloak/keycloak/issues/10699
Comment 5 RHEL Program Management 2023-09-09 07:28:36 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 7 RHEL Program Management 2023-09-12 13:05:58 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 8 RHEL Program Management 2023-09-12 13:10:58 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.