access.conf, In The Stack And Proven With PAM Itself

EL ships /etc/security/access.conf with no active rule and pam_access is not in the stack to read it, so every account is admitted from anywhere. This role writes the policy, adds the module through authselect, and refuses to write a rule set that would lock out the account running it. The live test asks PAM, with the origin set. Original role, live-tested on Rocky Linux 10.

This is the operations reference: version drift, dependants and neighbours. For what the module provisions, its inputs and outputs, and how to buy it, see the catalogue entry.

ansibleMulti-cloud & platform-agnosticSecurity & Identityv1.0.0live-tested

Provider drift

This artifact declares no Terraform provider requirements, so there is nothing to drift. Provider freshness applies to Terraform and OpenTofu modules.

What depends on this

No reference architecture names this module, so changing it affects only configurations that reference it directly.

Nearest alternatives

Same cloud, same category. These are what you would weigh against it without changing provider.

AIDE, A Baseline And A Timer That Notices A Change Authelia SSO Portal, Secrets Kept Out Of The Config, Proven By A Login Bandit, A shell=True Call Found At High Severity Boundary, Run To The Controller's Door Twice Dockle, A Root-User Finding With An Exit Code Gitleaks, A Planted Key Found Grype, Checked Against The Published Checksums Hard Limits For Logins And For Services, Which Are Not The Same

The same job on other clouds

This module has no cross-cloud peer set in the catalogue, so there is no portability comparison to draw.

Installing it

module "ansible_pam_access" {
  source  = "www.iac-bazaar.com/iac-bazaar/ansible-pam-access/any"
  version = "1.0.0"
}

A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.