Learn more about these different git repos.
Other Git URLs
Currently the users have several options for controlling the AD access control. One is the AD access provider that currently checks for expiration, one is the simple access provider and some users choose to configure the LDAP access provider as well.
We should summarize and document these options on wiki page.
design: => https://fedorahosted.org/sssd/wiki/DesignDocs/ActiveDirectoryAccessControl
design_review: 0 => 1
milestone: NEEDS_TRIAGE => SSSD 1.11.2
rhbz: => 0
Creating the document did not block 1.11.2, moving to 1.11.3 and setting higher priority so that the document is done in time.
milestone: SSSD 1.11.2 => SSSD 1.11.3
Moving tickets that didn't make 1.11.3 to 1.11.4
milestone: SSSD 1.11.3 => SSSD 1.11.4
owner: somebody => sbose
summary: Document the best practices for AD access control => MAN: Document the best practices for AD access control
After some more discussion with Sumit it would make more sense to document the access control on the wiki rather than the man pages. The first draft of the AD provider wiki page that will include this topic was shared between me and Sumit so far.
This ticket should not block 1.11.4
milestone: SSSD 1.11.4 => SSSD 1.11.5
summary: MAN: Document the best practices for AD access control => Document the best practices for AD access control
The wiki page itself is shaping up:
but the access control content is not there yet. Moving out of 1.11.5 as wiki page edits shouldn't block a release.
milestone: SSSD 1.11.5 => SSSD 1.11.6
Per conversation with Sumit, we just need to link the simple AD man pages to the wiki. Can be done post-release.
milestone: SSSD 1.11.6 => SSSD 1.11.7
milestone: SSSD 1.11.7 => NEEDS_TRIAGE
milestone: NEEDS_TRIAGE => SSSD 1.12.2
priority: major => trivial
We need to do a release as requested by downstream. Moving tickets that are not fixed already or very close to acking to 1.12.3
milestone: SSSD 1.12.2 => SSSD 1.12.3
mark: => 0
milestone: SSSD 1.12.3 => SSSD 1.12.4
Moving tickets that didn't make the 1.12.4 release to 1.12.5
milestone: SSSD 1.12.4 => SSSD 1.12.5
resolution: => fixed
sensitive: => 0
status: new => closed
Metadata Update from @jhrozek:
- Issue assigned to sbose
- Issue set to the milestone: SSSD 1.12.5
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:
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.
to comment on this ticket.