Bug 1030421 - man: document that the default access provider in AD provider is "permit"
Summary: man: document that the default access provider in AD provider is "permit"
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sssd
Version: 7.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Jakub Hrozek
QA Contact: Kaushik Banerjee
Depends On:
TreeView+ depends on / blocked
Reported: 2013-11-14 12:18 UTC by Jakub Hrozek
Modified: 2020-05-02 17:22 UTC (History)
6 users (show)

Fixed In Version: sssd-1.11.2-4.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-06-13 10:28:20 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 3007 0 None None None 2020-05-02 17:22:46 UTC

Description Jakub Hrozek 2013-11-14 12:18:45 UTC
This bug is created as a clone of upstream ticket:

This came up on sssd-users:

The default access_provider [for the AD provider] is "permit" because basically all of the real access providers require configuration to be useful and otherwise default to blocking everyone. Essentially, we elected to behave like FreeIPA with the ALLOW_ALL HBAC rule for initial setup.

This should be spelled out in the man page.

Comment 2 Amith 2014-01-07 13:09:46 UTC
Verified the bug on SSSD Version: sssd-1.11.2-13.el7

The man page for sssd-ad has been updated with the following NOTES section:

       The AD access control provider checks if the account is expired. It has the same effect as the following configuration of the LDAP

           access_provider = ldap
           ldap_access_order = expire
           ldap_account_expire_policy = ad

       However, unless the “ad” access control provider is explicitly configured, the default access provider is “permit”.

Comment 3 Ludek Smid 2014-06-13 10:28:20 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.

Note You need to log in before you can comment on or make changes to this bug.