Learn more about these different git repos.
Other Git URLs
In cases when SSSD is connected directly to AD and once a general mechanism of GPO download covered in ticket #1644 is implemented we need to implement the interpretation of the AD HBAC GPO into SSSD HBAC and enforce it.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.10 beta owner: somebody => yelley
rhbz: => todo
selected: => Not need
Moving tickets that are not a priority for SSSD 1.10 into the next release.
milestone: SSSD 1.10 beta => SSSD 1.11 beta
changelog: => A common use case for managing computer-based access control in an AD environment is through the use of two specific GPO policy settings. This RFE added support for this use case by enhancing the SSSD AD provider to include the GPO support necessary for this access control use case milestone: SSSD 1.13 beta => SSSD 1.12.0 review: => 0
design: => https://fedorahosted.org/sssd/wiki/DesignDocs/ActiveDirectoryGPOIntegration
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1115429
rhbz: todo => [https://bugzilla.redhat.com/show_bug.cgi?id=1115429 1115429]
patch: 0 => 1
As agreed with Yassir on IRC, let's keep the ticket open until the remaining tasks are done.
milestone: SSSD 1.12.0 => SSSD 1.12.1
Mass-moving all tickets that didn't make 1.12.1 into 1.12.2
milestone: SSSD 1.12.1 => SSSD 1.12.2
As discussed on last week's SSSD meeting, the feature was included in sssd. We are tracking a couple of bugs separately.
The relevant commits were:
resolution: => fixed status: new => closed
Metadata Update from @dpal: - Issue assigned to yelley - Issue set to the milestone: SSSD 1.12.2
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/2687
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.