Learn more about these different git repos.
Other Git URLs
The discussion is described in the following mail thread:
https://fedorahosted.org/pipermail/sssd-devel/2010-July/004255.html
In a nutshell: HBAC rules are good for access of a group of users to group of the machines. They are not good for expressing "Each user has his own laptop and he can log into his laptop".
Fields changed
summary: Allow simplified centalrally managed access control for host owners to the hosts => Allow simplified centrally managed access control for host owners to the hosts
milestone: NEEDS_TRIAGE => SSSD 1.6.0
I think this case is probably handled sufficiently by the use of the simple access provider and puppet to manage the sssd.conf.
This configuration should be documented.
coverity: => description: The discussion is described in the following mail thread:
In a nutshell: HBAC rules are good for access of a group of users to group of the machines. They are not good for expressing "Each user has his own laptop and he can log into his laptop". => The discussion is described in the following mail thread:
In a nutshell: HBAC rules are good for access of a group of users to group of the machines. They are not good for expressing "Each user has his own laptop and he can log into his laptop". doc: 0 => 1 owner: somebody => sgallagh priority: major => minor type: enhancement => task upgrade: => 0
component: SSSD => Documentation patch: => 0
Bug moved to https://bugzilla.redhat.com/show_bug.cgi?id=710254
resolution: => wontfix status: new => closed
Metadata Update from @dpal: - Issue assigned to sgallagh - Issue set to the milestone: SSSD 1.6.0
Metadata Update from @jhrozek: - Custom field rhbz adjusted to 0
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/1633
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.