Learn more about these different git repos.
Other Git URLs
When user is authenticated via pam_sss, any of the configured sssd domain would have been used. Having alice authenticated could mean it's email@example.com or firstname.lastname@example.org or email@example.com.
It'd be useful if the domain that was used to authenticate the user was available to the caller upon successful authentication / access check.
I propose pam_putenv of AUTH_DOMAIN value to be added.
milestone: NEEDS_TRIAGE => SSSD 1.13 beta
blocking: => 2151
rhbz: => todo
Let's revive when we resume the work on the containerized sssd.
milestone: SSSD 1.13 beta => SSSD 1.13 backlog
priority: major => minor
Mass-moving tickets not planned for the next two releases.
Please reply with a comment if you disagree about the move..
milestone: SSSD 1.13 backlog => SSSD 1.15 beta
Actually after talking to Dmitri again, moving to 1.13 backlog, this might be useful for integration effort.
milestone: SSSD 1.15 beta => SSSD 1.13 backlog
Re-setting priority of 1.13 backlog tickets used for planning.
priority: minor => major
Jan requested this ticket sooner.
milestone: SSSD 1.13 backlog => SSSD 1.13 alpha
rhbz: todo => 0
owner: somebody => mzidek
sensitive: => 0
patch: 0 => 1
milestone: SSSD 1.13 alpha => SSSD 1.13 beta
milestone: SSSD 1.13.1 => SSSD 1.13.2
This is important for the multitenancy case, but we're already trying to stabilize 1.13..moving to 1.14.
milestone: SSSD 1.13.2 => SSSD 1.14 beta
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1201262 (Red Hat Enterprise Linux 7)
rhbz: 0 => [https://bugzilla.redhat.com/show_bug.cgi?id=1201262 1201262]
Because the bugzilla linked to this ticket was about sssd running in a container and this ticket is more about better support for Apache modules and similar 3rd party integration, I'm removing the bugzilla link.
Moreover, it looks like Jan doesn't need this ticket implemented in the immediate future, so I'm also moving the ticket to the 1.14 backlog.
milestone: SSSD 1.14 beta => SSSD 1.14 backlog
rhbz: [https://bugzilla.redhat.com/show_bug.cgi?id=1201262 1201262] => todo
Since the 1.14 branch is transitioning into maintenance mode and new functionality is being developed in master which will become 1.15 eventually, I'm mass-moving tickets from the 1.14 backlog milestone to the "Future releases" milestone.
milestone: SSSD 1.14 backlog => SSSD Future releases (no date set yet)
Metadata Update from @adelton:
- Issue assigned to mzidek
- Issue marked as blocked by: #2151
- Issue set to the milestone: SSSD Future releases (no date set yet)
Metadata Update from @thalman:
- Custom field blocking reset (from 2151)
- Custom field design_review reset (from 0)
- Custom field mark reset (from 0)
- Custom field patch adjusted to on (was: 1)
- Custom field review reset (from 0)
- Custom field sensitive reset (from 0)
- Custom field testsupdated reset (from 0)
- Issue close_status updated to: None
- Issue tagged with: Canditate to close
Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.
Given that we are unable to fulfill this request I am closing the issue as wontfix.
If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.
Thank you for understanding.
Metadata Update from @pbrezina:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)
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.