The quarkus_flags scenario added in #445 is the only role-based
scenario without the roles -> ../../roles symlink, so in CI its
converge stops with "the role 'keycloak_quarkus' was not found".
Once the role is found, verify fails next: it reads
/opt/keycloak/keycloak-26.7.3/conf/keycloak.conf, but the scenario
installs the role's default version, which is no longer 26.7.3.
Add the roles symlink the other scenarios use and read keycloak.conf
through the /opt/keycloak/keycloak-*/ glob already used in
molecule/quarkus/verify.yml, so the check does not depend on the
installed version. The assertions are unchanged.
Update the keycloak_quarkus role defaults, argument specs, README and
molecule scenarios to the current upstream releases. Keycloak 26.7.4,
26.7.5, 26.8.0 and 26.8.1 together fix more than 40 CVEs, among them
CVE-2026-17526 (impersonation role can impersonate a realm admin) and
CVE-2026-94000 (manage-users delegated admin can become realm-admin).
The RHBK default moves from the 26.4 to the 26.6 stream. RHBK 26.6.7
(RHSA-2026:68278) fixes 28 CVEs; 26.4.16, the latest 26.4 release
from the same day, fixes 7 of them.
- keycloak_quarkus_version: 26.7.3 -> 26.8.1
- rhbk_version: 26.4.15 -> 26.6.7
- molecule/quarkus: SPID provider 26.7.1 -> 26.8.1 (new sha256),
keycloak-kerberos-federation 26.7.3 -> 26.8.1
- molecule/quarkus_upgrade: prepare on 26.7.3, converge to 26.8.1
JDBC driver defaults are left unchanged; they still match the versions
listed in Red Hat article 7033107 referenced from the defaults file.
Keycloak can require a user profile attribute only when one of the given
client scopes is requested, but the module's argument spec only accepted
required.roles and rejected required.scopes.
- drop the debian scenario from CI: the Debian mirrors are blocked on
the CI network
- quarkus_upgrade, https_revproxy: drop unused fixed published_ports
- debian: fetch the openid configuration from the instance with
ansible.builtin.uri instead of curl | jq on the controller
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Since the molecule jobs moved to self-hosted container runners, molecule
talks to a Docker daemon that does not share the runner's filesystem or
network namespace:
- quarkus_ha*: drop the postgresql.conf bind mount (the workspace path
does not exist on the daemon side) and pass listen_addresses via -c
- quarkus, quarkus_devmode: fetch the openid configuration from the
instance with ansible.builtin.uri instead of curl | jq on the runner,
and drop the fixed host published_ports that are no longer needed
- quarkus_nohost: add the missing roles symlink
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Check mode compared the realm returned by Keycloak with a plain
dict.update() of the module parameters. Keycloak stores attributes,
browserSecurityHeaders and smtpServer as string maps, merges attributes
and browserSecurityHeaders into the existing values and masks the SMTP
password, so the comparison never matched and check mode always
reported a change while a live run reported ok.
Predict the realm Keycloak would return for those maps in check mode
and add molecule checks for unchanged and changed settings.
Fixes#447
Signed-off-by: sarankumar1325 <120080287+sarankumar1325@users.noreply.github.com>
In check mode, the desired group memberships were built as a set and
compared with the stored memberships, a list, through is_struct_included().
It has no branch for sets and falls back to comparing their string forms,
which never match, so check mode reported a change for every existing user,
with or without groups.
Check mode now decides like normal mode: a group given by name or by path
counts as joined when the user is already a member. That rule moves from
update_user_groups_membership() into
filter_groups_to_add_to_and_remove_from_user(), which both modes use, and
the groups reported in check mode no longer list a group given by path
twice. Add check mode tests, including groups given by path.
Fixes#442
Signed-off-by: Filipe Rosa Capela <Filipe.Capela-CIC.Netherlands1@ibm.com>
Replace hostname-based health check URL with localhost. The health check
runs on the managed host itself, so it should always target localhost
rather than the public-facing keycloak_quarkus_hostname which can be
empty or a domain name behind a load balancer.
Compose the URL directly from existing production variables
(keycloak_quarkus_http_enabled, keycloak_quarkus_http_port,
keycloak_quarkus_https_port, keycloak_quarkus_http_relative_path)
without introducing intermediate variables.
Add .config/molecule/config.yml with shared molecule settings and a new
quarkus_nohost test scenario that verifies the role works when
keycloak_quarkus_hostname is left at its default empty value.
Fixes#428
Update the keycloak_quarkus role defaults, argument specs, README and
molecule scenarios to the current upstream releases. Keycloak 26.7.2+
and RHBK 26.4.15 fix CVE-2026-18963 (GHSA-4gv3-mc9p-5wqc, CVSS 9.1).
- keycloak_quarkus_version: 26.6.2 -> 26.7.3
- rhbk_version: 26.4.11 -> 26.4.15
- molecule/quarkus: SPID provider 26.5.6 -> 26.7.1 (new sha256),
keycloak-kerberos-federation 26.6.3 -> 26.7.3
- molecule/quarkus_upgrade: prepare on 26.6.2, converge to 26.7.3
JDBC driver defaults are left unchanged; they still match the versions
listed in Red Hat article 7033107 referenced from the defaults file.
When ~/.netrc contains an entry matching the Keycloak host, open_url()
silently replaces the OIDC Bearer header with Basic auth, causing 401
errors. Add use_netrc option (default false) to all keycloak modules
and pass it through to both open_url() call sites.
Includes molecule test scenario (netrc) that verifies both behaviors:
- default use_netrc=false ignores .netrc (fix works)
- use_netrc=true picks up .netrc and gets 401 (proves the bug)
Fixes: https://github.com/ansible-middleware/keycloak/issues/403
The parents branch of get_group_by_name() queried
GET /admin/realms/{realm}/groups/{id}/children?search=&exact=true
unconditionally. That endpoint only accepts GET from Keycloak 23 on, so
older servers (RH-SSO 7.x included) failed with 405 Method Not Allowed,
and 23/24 ignore search/exact and return only the first 10 children, so
subgroups past the tenth were silently reported as absent.
The lookup now goes through get_subgroups(), which already detects the
server generation, and that helper takes an optional search argument so
the search optimization is kept where the server supports it.
Use removesuffix to strip overlapping path from hostname before
re-appending http_relative_path, preventing /auth/auth/ duplication.
Add molecule test for the relative path scenario.
Keycloak 26 introduced Organizations as a stable feature for B2B
multi-tenancy within a single realm. This adds declarative Ansible
module support so organizations can be managed like other Keycloak
resources instead of requiring direct REST API calls.
New modules:
- keycloak_organization: CRUD for organizations with full check_mode,
diff_mode, and idempotency support. Manages name, alias, description,
enabled state, domains, and attributes.
- keycloak_organization_info: read-only module to list/search
organizations by name with exact or partial matching.
Also adds 6 API methods to the KeycloakAPI class and comprehensive
Molecule integration tests covering create, idempotency, update,
info queries, attributes, and delete flows.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Include keycloak_quarkus_http_relative_path in health_url construction
- Use rstrip('/') to handle both default '/' and custom paths like '/auth'
- Replace hardcoded 'master' realm with keycloak_quarkus_master_realm variable
- Add keycloak_quarkus_validate_certs option for SSL certificate validation
- Update documentation in meta and README
Fixes#299