Bug 1673716
| Summary: | Rebase k-h-c-i to version 0.8 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jakub Hrozek <jhrozek> |
| Component: | keycloak-httpd-client-install | Assignee: | Jakub Hrozek <jhrozek> |
| Status: | CLOSED ERRATA | QA Contact: | Scott Poore <spoore> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.0 | CC: | mkosek, spoore |
| Target Milestone: | rc | Keywords: | Rebase |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | sync-to-jira | ||
| Fixed In Version: | keycloak-httpd-client-install-0.8-1.el7 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-08-06 12:56:42 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Jakub Hrozek
2019-02-07 20:45:13 UTC
Verified. Version :: [root@sp1 ~]# rpm -q keycloak-httpd-client-install keycloak-httpd-client-install-0.8-1.el7.noarch Results :: Version has been updated as expected. Also ran a couple regression tests: [root@sp1 ~]# sh -x test1 + echo Secret123 + keycloak-httpd-client-install --client-originate-method registration --keycloak-server-url https://idp.keycloak.test:8443 --keycloak-admin-username admin --keycloak-admin-password-file - --app-name example_app --keycloak-realm demorealm --mellon-https-port 8443 --mellon-root mellon_root --mellon-protected-locations /private --force ValueError: Invalid protected location "/private/" must be equal to or ancestor of the mellon root "/mellon_root/" ^^^^ correct expected failure ^^^^ [root@sp1 ~]# sh -x test2 + echo Secret123 + keycloak-httpd-client-install --client-originate-method registration --keycloak-server-url https://idp.keycloak.test:8443 --keycloak-admin-username admin --keycloak-admin-password-file - --app-name example_app --keycloak-realm demorealm --mellon-https-port 8443 --mellon-root mellon_root --mellon-protected-locations /mellon_root --force [Step 1] Connect to Keycloak Server [Step 2] Create Directories [Step 3] Set up template environment [Step 4] Set up Service Provider X509 Certificiates [Step 5] Build Mellon httpd config file [Step 6] Build Mellon SP metadata file [Step 7] Query realms from Keycloak server [Step 8] Create realm on Keycloak server [Step 9] Query realm clients from Keycloak server [Step 10] Get new initial access token [Step 11] Creating new client using registration service [Step 12] Enable saml.force.post.binding [Step 13] Add group attribute mapper to client [Step 14] Add Redirect URIs to client [Step 15] Retrieve IdP metadata from Keycloak server [Step 16] Completed Successfully ^^^^ good pass. also after setting up apache dirs authenticated with user ^^^^ [root@sp1 ~]# sh -x test3 + echo Secret123 + keycloak-httpd-client-install --client-originate-method registration --keycloak-server-url https://idp.keycloak.test:8443 --keycloak-admin-username admin --keycloak-admin-password-file - --app-name example_app --keycloak-realm master --mellon-https-port 8443 --mellon-root mellon_root --mellon-protected-locations /mellon_root/private --force [Step 1] Connect to Keycloak Server [Step 2] Create Directories [Step 3] Set up template environment [Step 4] Set up Service Provider X509 Certificiates [Step 5] Build Mellon httpd config file [Step 6] Build Mellon SP metadata file [Step 7] Query realms from Keycloak server [Step 8] Use existing realm on Keycloak server [Step 9] Query realm clients from Keycloak server [Step 10] Force delete client on Keycloak server [Step 11] Get new initial access token [Step 12] Creating new client using registration service [Step 13] Enable saml.force.post.binding [Step 14] Add group attribute mapper to client [Step 15] Add Redirect URIs to client [Step 16] Retrieve IdP metadata from Keycloak server [Step 17] Completed Successfully Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:2137 |