Add roles/ad_integration#263
Open
markuslf wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
New
ad_integrationrole: a thin wrapper around the upstreamfedora.linux_system_roles.ad_integrationrole, analogous to the existingnetworkandkernel_settingswrappers. It joins a host to an Active Directory domain (realm join+ SSSD configuration) so AD users can log in and AD groups can be used for access control andsudo.Motivated by the manual
realm join/sssd.confsteps still documented in several*/rst/03-infra.rstcustomer docs (e.g. projects 163, 178, 223). FreeIPA remains the Linuxfabrik standard (freeipa_client); this covers the AD-join exceptions.Design
__role_var/__dependent_var/__group_var/__host_var/__combined_var).ad_integration__logindict (username/password), Bitwarden-lookup friendly. No default secrets.combine_lod(unique_key="key").manage_timesync,manage_crypto_policiesandmanage_dnssub-features are intentionally NOT exposed. Time sync, DNS and crypto policy stay with the dedicated LFOps roles (chrony,network,crypto_policy). Documented in the README.Deliverables (per CONTRIBUTING)
roles/ad_integration/(defaults,meta/argument_specs.yml,tasks,README.md)playbooks/ad_integration.ymlplaybooks/all.yml,playbooks/README.md,COMPATIBILITY.md,CHANGELOG.mdValidation
argument_specsrejects missing mandatory__realm/__login; passes when provided.client_software=winbind), handoff to the upstream role works, timesync/crypto/DNS correctly not triggered.COMPATIBILITY.mdmarks all platforms(x)(theoretically usable, untested) since the role was not tested against a live AD. Raise toxonce it runs in a real project.