#3443 [rfe] sssd should be able to process host-based security filtering when processing active directory gpos
Closed: cloned-to-github 2 years ago by pbrezina. Opened 4 years ago by jhrozek.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1462348

[+] Description of problem:
 - Active Directory GPOs which are applied to Linux hosts per their security
filtering should be properly handled by SSSD.  At the moment, GPOs can only be
applied to Linux hosts which live within the OU that the GPO is linked to.

Metadata Update from @jhrozek:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1462348

4 years ago

Metadata Update from @jhrozek:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1462348

4 years ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.15 backlog

4 years ago

Metadata Update from @jhrozek:
- Issue priority set to: major
- Issue set to the milestone: SSSD 1.16.0 (was: SSSD 1.15 backlog)

4 years ago

Since we are required to release a new upstream tarball no later than Friday Oct-20, I'm moving tickets that will not be closed by that date to the next milestone, 1.16.1

Metadata Update from @jhrozek:
- Issue assigned to mzidek
- Issue set to the milestone: SSSD 1.16.1 (was: SSSD 1.16.0)
- Issue tagged with: PR

4 years ago

Even though I'm adding the postponed-to-2.0 tag, if we manage to review and test the code sooner, I'm fine with moving the ticket back to the earliest available milestone.

Metadata Update from @jhrozek:
- Issue tagged with: postpone-to-2-0

4 years ago

The flags for this issue are wrong. There is no PR or code for this RFE so far, so there should be no PR flag. I think it got mixed with some other issue that had PR. The 1.16.1 flag was also never realistic for this change.

Sorry I did not notice this sooner. Ack to the postpone-to-2.0 flag.

Metadata Update from @mzidek:
- Issue untagged with: PR

4 years ago

Thank you, I mixed this PR with the one from Thor. I think this should be postponed to future releases and not to 2.0

Metadata Update from @jhrozek:
- Issue untagged with: postpone-to-2-0
- Issue tagged with: postpone-to-future-releases

4 years ago

Metadata Update from @jhrozek:
- Issue untagged with: postpone-to-future-releases
- Issue set to the milestone: SSSD Future releases (no date set yet) (was: SSSD 1.16.1)

4 years ago

Metadata Update from @thalman:
- Issue tagged with: bugzilla

2 years ago

Metadata Update from @thalman:
- Issue tagged with: Future milestone

2 years ago

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/4470

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @pbrezina:
- Issue close_status updated to: cloned-to-github
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata