SSSD access providers decide who can log in after identity lookup
SSSD access providers decide who can log in after identity lookup Identity lookup and login authorization are separate decisions. SSSD can use one provider to find a user and another setting to decide whether that user
SSSD access providers decide who can log in after identity lookup
Identity lookup and login authorization are separate decisions. SSSD can use one provider to find a user and another setting to decide whether that user may access the local system. When teams review directory authentication only, a valid account may remain able to log in long after its group, employment state, or host assignment changed.
Red Hat's SSSD documentation describes access_provider as the component that evaluates which users are granted access to the system. It supports a simple allow or deny list and an LDAP-backed filter. Offline caching adds another condition: the documentation says SSSD checks whether the user's most recent online login attempt was successful.
Make the intended population explicit
For a small set of operations teams, a simple group policy is easy to review.
[domain/example.net]
id_provider = ldap
auth_provider = ldap
ldap_uri = ldaps://directory.example.net
access_provider = simple
simple_allow_groups = linux-admins, production-operators
Use the group names and provider settings that match the deployed directory. The example shows the shape of the policy, not a substitute for a tested sssd.conf.
The access policy should distinguish authentication from authorization. A directory account can authenticate and still be denied local login. A cached account can be present in NSS while the access provider denies a fresh session. Test both conditions separately.
Offline behavior needs a decision
If the directory is unavailable, an online-only access check may prevent login or may allow cached behavior depending on configuration. Decide which outcome is correct for each host class. A laptop used by an administrator away from the network has different needs from a production server with a directory outage.
Review cached credentials, the most recent login result, group membership caching, and the lifetime of those values. If a user was disabled, removed from an allow group, or moved to a different host population, confirm that the local session and the next login are both denied according to policy.
Test the whole account lifecycle
Build a test matrix for an allowed user, a denied user, a disabled account, a group that matches a nested directory rule, an offline host, a stale cache, and a changed host assignment. Use sssctl and the SSSD logs to see which provider returned a result. Do not rely on a successful id command as proof that login authorization passed.
Restrict who can edit sssd.conf and the directory filters. A permissive LDAP access filter can turn an authentication service into a broad account gateway. Log the provider, domain, user, decision, and reason at a level that supports an access review without exposing directory secrets.
The final inventory should list each host's domain, access provider, allowed groups or filter, offline policy, and review owner. That record makes the separation between "the directory knows this user" and "this host permits this user" visible to the teams that operate each side.
References
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.