#2187 [RFE] Expose different identity domains to different D-BUS consumers
Closed: wontfix 4 years ago by pbrezina. Opened 10 years ago by dpal.

SSSD will be a common storage for all identity info coming from different sources, however not all consumers of these sources should be able to see all the information. It should be possible to check the identity if the connecting D-BUS client and serve only a subset of domains to this consumer. This would allow separating the identities exposed over the NSS responder and over the D-BUS responder i.e separating login applications from the web applications.

There was a ticket like this in the past but I could not find it. We might have deferred or closed it.


Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.12 beta
rhbz: => 0

Fields changed

milestone: SSSD 1.12 beta => 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

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

I'm moving all D-Bus related tickets to 1.12.4. We are working on the interfaces in the 1.12 cycle, but as the interface won't be ready for 1.12.3 release anyway, it makes sense to realign all D-Bus tickets in 1.12.4

mark: => 0
milestone: SSSD 1.12.3 => SSSD 1.12.4

The sbus-related patches are landing on the list, but we realized during review that they're too big for 1.12, at least for the time being. We're going to commit them to master only for now and backport on request to avoid breaking 1.12.

milestone: SSSD 1.12.4 => SSSD 1.13 alpha
owner: somebody => pbrezina

Should not block Alpha

milestone: SSSD 1.13 alpha => SSSD 1.13 beta
sensitive: => 0

We need to make room for newly filed tickets in 1.13.

milestone: SSSD 1.13 beta => SSSD 1.13 backlog

At the moment we don't plan on implementing this in the next upstream release. Patches are welcome.

milestone: SSSD 1.13 backlog => SSSD 1.15 beta

Metadata Update from @dpal:
- Issue assigned to pbrezina
- Issue set to the milestone: SSSD Future releases (no date set yet)

7 years ago

Metadata Update from @pbrezina:
- Assignee reset

4 years ago

Metadata Update from @thalman:
- Custom field design_review reset (from 0)
- Custom field mark reset (from 0)
- Custom field patch reset (from 0)
- 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

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

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