#2438 [RFE] Make it possible to use different Unix socket path, use it for distinguishing domains
Closed: wontfix 4 years ago by pbrezina. Opened 9 years ago by adelton.

Currently, the nss module does not allow to change the Unix socket. However, if sssd supported multiple sockets, they could be mapped to various containers (and in the container they would show up in the default location), and sssd could start making some access or namespace (domain) decisions based on the socket the client is connecting through.


This should be considered in the context of #2151

milestone: NEEDS_TRIAGE => SSSD 1.13 beta

Fields changed

blocking: => 2151

Fields changed

mark: => 1

Fields changed

rhbz: => 0

We can revive this ticket when we think about supporting the containerized use-case again.

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

Metadata Update from @adelton:
- Issue marked as blocked by: #2151
- Issue set to the milestone: SSSD Future releases (no date set yet)

7 years ago

Metadata Update from @thalman:
- Custom field blocking reset (from 2151)
- Custom field design_review reset (from 0)
- Custom field mark adjusted to on (was: 1)
- Custom field patch reset (from 0)
- Custom field review reset (from 0)
- Custom field testsupdated reset (from 0)
- Issue close_status updated to: None
- Issue tagged with: Canditate to close

4 years ago

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)

4 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/3480

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.

Login to comment on this ticket.

Metadata